Interactives - Usercomm - DB2 V10 Hold Data and Cover Letters for HP Release level AF00

1ACF0C038 ACF2 LOGONID ATTRIBUTES HAVE REPLACED DEFAULT USER ATTRIBUTES
 READY
  %COVRLETR WDB2I.R.DB2101S.SMPPTS
 IKJ56247I FILE LNKLST NOT FREED, IS NOT ALLOCATED

 UI11697 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM96567 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS users of CURSOR WITH HOLD   *
        *                 on declared global temporary tables (DGTT)   *
        *                 (or SCROLL CURSOR WITH HOLD on base table,   *
        *                 which builds internal DGTTs) who have        *
        *                 applied APAR PM83642 (DB2 10 PTF UK94441,    *
        *                 DB2 9 PTF UK94442)                           *
        ****************************************************************
        * PROBLEM DESCRIPTION: After applying APAR PM83642 (UK94441/   *
        *                      UK94442), users of CURSOR WITH HOLD on  *
        *                      DGTT or SCROLL CURSOR WITH HOLD on base *
        *                      table may experience RC00C90101         *
        *                      DSNGDCMT ERQUAL500E, followed by DB2    *
        *                      crash RC00D94001 or RC00D93001          *
        *                      MSGDSNV086E                             *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        After applying PM83642 (UK94441/UK94442), RC00C90101 DSNGDCMT
        ERQUAL500E abend occurred in the following DGTT WITH HOLD
        scenarios:

        Case 1:
        Application with CURSOR WITH HOLD on a DGTT (or SCROLL CURSOR
        WITH HOLD on a base table) experienced cancel/abort of some
        kind. RC00C90101 DSNGDCMT ERQUAL500E abend occurred during abort
        processing.

        Case 2:
        Application with CURSOR WITH HOLD on a DGTT had a DGTT index
        defined and performed DDL DROP TABLE on the DGTT before the
        cursor was closed. RC00C90101 DSNGDCMT ERQUAL500E abend
        occurred during the subsequent commit.

        In both cases, DB2 went down because RC00C90101 DSNGDCMT
        ERQUAL500E abend occurred during must-complete processing.

        The reason for the abend was that the internal CTDB structure
        for local DBD for Workfile database was still present at the
        time when this local DBD was being freed.

        The reason that the local CTDB has persisted is that APAR
        PM83642 added code which ensures that the CTDB does not get
        freed it there are any held CUBs in Workfile database present.

        However, in the case of DGTT abort processing such as in Case 1
        above, a held CUB may not necessarily be freed until storage
        pool goes away at deallocation time and therefore it should be
1       acceptable for the CTDB to be freed during abort time.

        For case 2, when the DGTT was dropped, any held DGTT index CUBs
        were invalidated and, by the time they were freed in subsequent
        commit, these CUBs may not have necessarily gone through the
        code that turns off their HOLD state. Therefore it should be
        acceptable for the CTDB to be freed during commit time.
        The following changes are made to the DB2 code:

        In thread abort processing in DM, there is no need to check
        CTDB for HOLD count, since any held CUBs are expected to be
        freed during deallocation anyway.

        If DGTT index CUB is being invalidated, turn off its HOLD state
        in DM code.

        For future cases of the aforementioned DBDM sanity check, a
        diagnostic dump will be attempted instead, to avoid bringing
        down DB2.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM96567
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNGDCMT  PM96567
       DSNICINV  PM96567
       DSNICMT2  PM96567

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM96567   DSNGDCMT DSNICINV DSNICMT2

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNGDCMT
       DSNICINV
       DSNICMT2

      LISTEND
 UI11697 COVER LETTER END


 UI11767 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM94844 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS users of referential        *
        *                 integrity, with dependent (child) table      *
        *                 containing variable length columns, where    *
        *                 SQL UPDATE of foreign key column moves row   *
        *                 from reordered row format (RRF) partition    *
        *                 to basic row format (BRF) partition or vice  *
        *                 versa                                        *
        ****************************************************************
1       * PROBLEM DESCRIPTION: SQLCODE -530 (new foreign key has no    *
        *                      parent key) may be issued by mistake    *
        *                      when SQL UPDATE of foreign key column   *
        *                      moves row from RRF partition to BRF     *
        *                      partition or vice versa                 *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        During SQL UPDATE of the foreign key column that involved cross-
        partition update such that the source and target partitions had
        different row formats, DB2 issued SQLCODE -530 (new foreign key
        has no parent key) even though the update should have been
        allowed.

        The reason for this problem is that the code that extracts the
        foreign key from the new row assumed that the target partition
        had the same row format as the source partition, which resulted
        in an incorrectly extracted foreign key value, which did not
        have a match in the parent table.

        For this problem to happen, the foreign key itself need not be
        of variable length. The problem may happen as long as the child
        table has one or more variable length columns.
        Code has been modified to work with the correct row format when
        extracting the foreign key from the new row during SQL UPDATE
        of the foreign key column.

        To bypass the problem until this APAR is applied, REORG can be
        run (potentially with the ROWFORMAT option) to ensure that the
        row formats of the source and target partitions match.

        Additional keywords: SQLCODE530 SQLUPDATE
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM94844
    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  PM94844
       DSNIRELK  PM94844
       DSNIRELV  PM94844

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM94844   DSNILREP DSNIRELK DSNIRELV

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNILREP
       DSNIRELK
       DSNIRELV

      LISTEND
 UI11767 COVER LETTER END

1
 UI11775 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM95615 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS, DB2 10 for z/OS, and     *
        *                 DB2 11 for z/OS users of ODBC/CLI running    *
        *                 in a zPDT environment.                       *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND 0C4 when processing an SQL        *
        *                      statement with embedded bracketed       *
        *                      comments.                               *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When an SQL statement is being scanned for embedded bracketed
        comments, a C strcpy instruction is used to copy one byte of
        data to an adjacent temporary buffer.  The one-byte source data
        is not declared as a C null-terminated string.  This results
        in the ending character not being recognized causing the source
        data to be copied repeatedly to the target until an invalid
        address was encountered.

        The abend only occurs when running in a zPDT environment.
        The IBM System z Personal Development Tool (zPDT) creates a
        virtual System z architecture environment that allows users to
        run z/OS and its relative software on a PC platform without
        the need for traditional System z hardware.
        Code has been updated with the C memcpy instruction replacing
        the strcpy instruction.  This will allow the code to move
        one byte of data without a null terminator.
    COMPONENT:  5740-XYR02-JDBAA17
    APARS FIXED: PM95615
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR02 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNAOG0T  PM95615
       DSNAOCLI  PM95615
       DSNAOSDK  PM95615

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM95615   DSNAOG0T DSNAOCLI DSNAOSDK

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNAOG0T
       DSNAOCLI

      MACROS
       DSNAOSDK

      LISTEND
 UI11775 COVER LETTER END
1

 UI11780 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM94911 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS      *
        *                 users of queries with equal predicates that  *
        *                 include a timestamp column and a string host *
        *                 variable.                                    *
        ****************************************************************
        * PROBLEM DESCRIPTION: Apar PM94911 is a pre-conditioning apar *
        *                      for PM73542, the enabling apar.         *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        This APAR provides the necessary pre-conditioning code for
        a later apar, PM73542.

        Apar PM73542 will provide a solution for the following problem.

        A performance regression can occur for a static SQL statement
        that contains an equal predicate with a TIMESTAMP column and a
        string host variable.


        The following example provides such a case.

        1. Create a Table T1 that uses a range partitioning scheme
            using a timestamp column.

           CREATE TABLE T1(INTCOL INT,
                           TSCOL  TIMESTAMP)
               PARTITION BY (TSCOL)
               (PARTITION 1 ENDING AT ('2020-01-01-00.00.00.000000'),
                PARTITION 2 ENDING AT ('2030-01-01-00.00.00.000000'),
                PARTITION 3 ENDING AT (MAXVALUE));


        2. The static query below contains an equal predicate on column
           TSCOL and a string host variable. DB2 may not choose page
           range screening (as shown by PAGE_RANGE='N' in the
           PLAN_TABLE) when an EXPLAIN is performed for the following
           SQL statement.

           EXEC SQL
           SELECT INTCOL INTO :HVINT1:IND1
           FROM  T1
           WHERE TSCOL  = :HVVCHAR2:IND2;

        Page range screening (PAGE_RANGE='Y') may not be chosen by DB2
        for the above static query.  However, for DB2 v9, the choice is
        more likely.

        DB2 did not correctly process the aforementioned SQL statement.
        This can cause a performance regression.
1       This apar adds the pre-conditioning code needed for a later
        enabling apar PM73542.

        Additional Keywords: SQLTIMESTAMP SQLHOSTVAR SQLACCESSPATH
                             SQLPERFORMANCE PAGERANGE
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM94911
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM92597:

        See PM92597 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM92597 corrects a problem of incorrect output for a query
        containing NOT DISTINCT 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.
      DB2BIND:
        ***Action for PM89230:

        See PM89230 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM89230 corrects a problem of an ABEND04E RC00E70005 at location
        DSNXGRDS DSNXGRM1 M258 for an SQL statement containing a graphic
        or vargraphic host variable which can be deleted.

        To make this fix effective for a static application, it must 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 PM85976:

        See PM85976 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM85976 corrects an ABEND0C4 at DSNXEBR OFFSET 441C or an
        ABEND04E RC00E70005 at location DSNXESX4 M999 can occur when
        executing the SET CURRENT OPTIMIZATION HINT = '' or the SET
        CURRENT SQLID = '' statements. These failures can occur from
        dynamic or static SQL when a UNICODE encoding scheme is
        employed.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      MULTSYS:
        ***Action for PM94911:
1
        PM94911 is a pre-conditioning APAR that includes changes to
        support a functional code change that will be enabled via
        APAR PM73542 at a later date. At this time, all of the changes
        are transparent to the user. In a data sharing group, this
        pre-conditioning APAR(PM94911) should be applied to all
        members before the later enabling APAR PM73542 is applied to
        any member. The code change is not enabled until the enabling
        APAR PM73542 is applied. PM73542 corrects a problem of
        performance regression for static SQL queries on tables that
        use a range partitioning scheme and have equal predicate on
        timestamp column and string host variable.
      ACTION:
        ***Action for PM94911:

        Please note that the following action needs to be performed
        along with the application of this apar/ptf.

        Please note that the application of this apar/ptf needs to be
        applied to all DB2 members in a datasharing environment.  This
        will allow all members to include both the needed bindtime and
        runtime code changes.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXEBR   PM94911
       DSNXEMG1  PM94911
       DSNXGOSQ  PM94911
       DSNXGRM1  PM94911
       DSNXGRSR  PM94911
       DSNXGRTM  PM94911
       DSNXGRTS  PM94911
       DSNXGSFN  PM94911
       DSNXRBND  PM94911

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM94911   DSNXEBR  DSNXEMG1 DSNXGOSQ DSNXGRM1 DSNXGRSR DSNXGRTM
                 DSNXGRTS DSNXGSFN DSNXRBND

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXEBR
       DSNXEMG1
       DSNXGOSQ
       DSNXGRM1
       DSNXGRSR
       DSNXGRTM
       DSNXGRTS
       DSNXGSFN
       DSNXRBND

      LISTEND
 UI11780 COVER LETTER END


 UI11793 COVER LETTER START
1   PROBLEM DESCRIPTION(S):
      PM96651 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS users of XML.               *
        ****************************************************************
        * PROBLEM DESCRIPTION: The following abend may occur when      *
        *                      inserting, updating, or loading XML     *
        *                      data:                                   *
        *                                                              *
        *                      ABEND04E RC00E2000D in module           *
        *                      DSNNXCMT.DSNSVSFB offset+08DA           *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When parsing a big XML document after parsing a small XML
        document, DB2 needed a bigger buffer to hold the parsed result
        or conversion result. If the request to free the storage of
        the original buffer or to allocate the storage of the bigger
        buffer failed, the buffer pointer was not cleared and still
        pointed to the original buffer.

        During abort processing,  DB2 tried to free the buffer
        storage again, causing DB2 to terminate abnormally.
        The DB2 for z/OS code was modified to clear out the pointer
        to the buffer used for XML parsing before freeing the
        original buffer or allocating the bigger buffer.

        Additional keywords: XMLALL DB2ABTERM SQLXML
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM96651
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNNOPAR  PM96651

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM96651   DSNNOPAR

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNNOPAR

      LISTEND
 UI11793 COVER LETTER END


 UI11797 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM96344 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 (NFM) for z/OS users of declared  *
        *                 global temporary tables (DGTT) who employ    *
        *                 partition-by-growth table spaces in Workfile *
1       *                 database                                     *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00E400A0 DSNUGACC+12E4       *
        *                      during DGTT application that uses a     *
        *                      partition-by-growth workfile table      *
        *                      space (PBG), potentially followed by    *
        *                      DB2 crash MSGDSNV086E RC00F30420        *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        During a partition-growing insert into a DGTT which was residing
        in a partition-by-growth workfile table space, the 0C4 abend
        occurred because the insert driver module was looking at the
        old (pre-growth) OBDPSET structure while thinking that it was
        looking at the new (post-growth) one.

        Specifically, in the old OBDPSET, the OBDPSP2L array slot did
        not exist for the newly grown partition and therefore the module
        was looking at an incorrect memory location. This made the
        module go to a wrong code path, which resulted in the
        aforementioned abend.
        Code has been changed to make sure that the OBDPSET structure
        is refreshed after growing a new partition, so that the insert
        driver module will have the latest structure at its disposal.

        Additional keywords: SQLPBG SQLDGTT
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM96344
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNISEGF  PM96344

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM96344   DSNISEGF

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNISEGF

      LISTEND
 UI11797 COVER LETTER END


 UI11880 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM93845 -
        ****************************************************************
        * USERS AFFECTED: AE PM87870 FIX COMPLETION                    *
        ****************************************************************
        * PROBLEM DESCRIPTION: AE PM87870 FIX COMPLETION               *
        ****************************************************************
        * RECOMMENDATION:                                              *
1       ****************************************************************
        AE PM87870 FIX COMPLETION
        AE PM87870 FIX COMPLETION
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM93845
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNIREPR  PM93845

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM93845   DSNIREPR

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIREPR

      LISTEND
 UI11880 COVER LETTER END


 UI11907 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89580 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of SQL  *
        *                 with EXTENDED INDICATOR enabled.             *
        ****************************************************************
        * PROBLEM DESCRIPTION: This APAR addresses TWO problems.       *
        *                                                              *
        *                      Problem 1.                              *
        *                                                              *
        *                      An ABEND0C4 RC38 at location DSNXGRDS   *
        *                      DSNXOVC +137A can occur when an SQL     *
        *                      statement satisfies the following list  *
        *                      of conditions.                          *
        *                                                              *
        *                      1. SQL is an UPDATE statement or a      *
        *                         SELECT statement with the            *
        *                         FOR UPDATE clause.                   *
        *                                                              *
        *                      2. The object table is a VIEW.          *
        *                                                              *
        *                      3. A target column defined in a VIEW    *
        *                         and referenced in the FOR UPDATE     *
        *                         list or in an UPDATE statement is    *
        *                         not allowed to be updated.           *
        *                                                              *
        *                      4. The EXTENDEDINDICATOR(YES) bind      *
        *                         option or the specification of       *
        *                         WITH EXTENDED INDICATORS prepare     *
        *                         attribute is used.                   *
        *                                                              *
1       *                                                              *
        *                      Problem 2.                              *
        *                                                              *
        *                      An SQLCODE -798 or -151 can be issued   *
        *                      incorrectly for an SQL statement that   *
        *                      satisfies the following conditions.     *
        *                                                              *
        *                      MERGE statement                         *
        *                       1. the target of the INSERT or UPDATE  *
        *                          operations of the MERGE statement   *
        *                          is a base table.                    *
        *                       2. a target column of                  *
        *                          modification-operation is defined   *
        *                          with generated always(in            *
        *                          generated-column-definition of the  *
        *                          base table) and specifies the null  *
        *                          value as the value of the column.   *
        *                       3. at least one input host variable    *
        *                          is specified for the other target   *
        *                          columns in modification-operation.  *
        *                                                              *
        *                      INSERT statement                        *
        *                       1. the object of the INSERT statement  *
        *                          is a base table.                    *
        *                       2. a target column for which insert    *
        *                          values are provided is defined      *
        *                          with generated always(in            *
        *                          generated-column-definition of the  *
        *                          base table) and specifies the null  *
        *                          value as the value of the column.   *
        *                       3. at least one input host variable    *
        *                          is specified for the other target   *
        *                          columns.                            *
        *                                                              *
        *                      UPDATE statement                        *
        *                       1. the object of the UPDATE statement  *
        *                          is a base table.                    *
        *                       2. a target column that is to be       *
        *                          updated is defined with generated   *
        *                          always(in                           *
        *                          generated-column-definition         *
        *                          of the base table) and specifies    *
        *                          the null value as the new value of  *
        *                          the column.                         *
        *                       3. at least one input host variable    *
        *                          is specified for the other target   *
        *                          columns.                            *
        *                                                              *
        *                      The EXTENDEDINDICATOR(YES) bind         *
        *                      option or the specification of          *
        *                      WITH EXTENDED INDICATORS prepare        *
        *                      attribute is used.                      *
        *                                                              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
1       The following example helps to illustrate the aforementioned
        problems.

        Step 1. Create a Table T1 and a View V1 on Table T1.

          CREATE TABLE T1
          (C1 CHAR(5),
           C2 INTEGER,
           C3 CHAR(5),
           C4 ROWID NOT NULL GENERATED ALWAYS
          ) ;

          CREATE VIEW V1(D1, D2, D3, D4) AS
            SELECT C1,
                   C2+1,
                   SUBSTR(C3,1,2),
                   C4
            FROM T1 ;


        Step 2. The application uses the EXTENDEDINDICATOR bind option.

          BIND PACKAGE(...) MEMBER(...)-
          EXTENDEDINDICATOR(YES) ....


        Step 3. The following two SQL statements can cause the
                ABEND0C4 mentioned above.

           An UPDATE statement with an extended indicator variable
           such as:

           main ()
           {
            ...
            DCL H1 INT;
            DCL M1 INT;
            ...

            UPDATE V1 SET D2 = :H1 :M1 ;
            ...
           }

           A SELECT FOR UPDATE statement, such as:

           main()
           {
              SELECT D1, D2, D3 FROM V1 FOR UPDATE OF D2 ;
           }


        Step 4. An UPDATE or INSERT SQL statement can cause an incorrect
                SQLCODE -151 or -798 to be issued. Such as

           main ()
           {
1           ...
            DCL H1 INT;
            DCL M1 INT;
            ...

            UPDATE T1 SET (C2, C4) = (:H1 :M1, NULL) ;
            ...
            INSERT INTO T1 (C2, C4) VALUES(:H1 :M1, NULL) ;
            ...
           }

        DB2 does not process the extended indicator variable properly
        which can result in the abend or an incorrect result.

        The bind time code in DB2 is modified to process extended
        indicator variables properly to avoid the unexpected abend.

        Additionally, DB2 is modified to issue an SQLCODE -151 properly
        at bind time when an UPDATE or SELECT FOR UPDATE statement,
        which references a VIEW and targets a column that cannot be
        updated, is prepared using WITH EXTENDED INDICATORS attribute or
        is contained within an application that uses the
        EXTENDEDINDICATOR(YES) bind option.

        Additional Keywords: SQLUPDATE SQLVIEW OFFSET137A SQLCODE151
                             SQLCODE798 SQLINCORR SQLINCORROUT
                             DB2INCORR/K EXTENDED INDICATORS

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89580
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOCAS  PM89580
       DSNXOVC   PM89580

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89580   DSNXOCAS DSNXOVC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOCAS
       DSNXOVC

      LISTEND
 UI11907 COVER LETTER END


 UI11909 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM95677 -
        ****************************************************************
        * USERS AFFECTED: All DB2 V9, 10 or 11 for z/OS users of an    *
1       *                 SQL statement that has a '*' in the SELECT   *
        *                 list and contains multiple outer joins with  *
        *                 one of them as a nested outer join.          *
        ****************************************************************
        * PROBLEM DESCRIPTION: Incorrect output, ABEND04E RC00C90101   *
        *                      at the location DSNGD001 DSNGDVRT 500B, *
        *                      or ABEND0C7 RC00000000 at the location  *
        *                      DSNXGRDS DSNXRTIM OFFSET7120(or         *
        *                      OFFSET6B98) could happen for an SQL     *
        *                      statement that has a '*' in the SELECT  *
        *                      list and contains multiple outer joins  *
        *                      with one of them as a nested outer      *
        *                      join.                                   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An example is shown below:

        CREATE TABLE T1 ( C1 CHAR(4) NOT NULL,
                          C2 CHAR(4) NOT NULL
                        );
        CREATE TABLE T2 ( C1 CHAR(4) NOT NULL,
                          C2 CHAR(4) NOT NULL
                        );
        CREATE TABLE T3 ( C1 CHAR(4) NOT NULL,
                          C2 CHAR(4) NOT NULL
                        );
        CREATE TABLE T4 ( C1 CHAR(4) NOT NULL,
                          C2 CHAR(4) NOT NULL
                        );

        INSERT INTO T1 VALUES('C11', 'C21');
        INSERT INTO T1 VALUES('C12', 'C22');
        INSERT INTO T1 VALUES('C01', 'C21');
        INSERT INTO T1 VALUES('C02', 'C22');
        INSERT INTO T2 VALUES('C11', 'C21');
        INSERT INTO T2 VALUES('C12', 'C22');
        INSERT INTO T3 VALUES('C11', 'C21');
        INSERT INTO T3 VALUES('C12', 'C22');
        INSERT INTO T4 VALUES('C11', 'C21');
        INSERT INTO T4 VALUES('C12', 'C22');

        SELECT T3.*
        FROM T1 LEFT OUTER JOIN
               (T2 INNER JOIN T3
                   ON T2.C1=T3.C1
                   LEFT OUTER JOIN T4
                   ON T2.C1=T4.C1)
               ON T1.C1=T3.C1
        ;

        The query above returned the result:('.' means an unprintable
        character)

          +-------------+
          |  C1  |  C2  |
1         +-------------+
        1_| .C11 | .C21 |
        2_| .C12 | .C22 |
        3_| .... | .... |
        4_| .... | .... |
          +-------------+

        While the correct result should be: ('?' means NULL)

          +-------------+
          |  C1  |  C2  |
          +-------------+
        1_| C11  | C21  |
        2_| C12  | C22  |
        3_| ?    | ?    |
        4_| ?    | ?    |
          +-------------+

        DB2 did not correctly process the aforementioned SQL statements,
        which caused the incorrect output or ABEND.
        DB2 has been modified to correctly process the aforementioned
        SQL statement, so there will be no incorrect output or ABEND.

        Additional keywords: SQLOUTERJOIN SQLFULLJOIN SQLOUTER SQLFULL
                             SQLJOIN SQLLEFTJOIN SQLLEFT SQLRIGHTJOIN
                             SQLRIGHT
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM95677
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM95677:

        See PM95677 APAR/PTF text for additional information about
        why a REBIND or recreate view is necessary.

        PM95677 corrects a problem that incorrect output, ABEND04E
        RC00C90101 at the location DSNGD001 DSNGDVRT 500B, or ABEND0C7
        RC00000000 at the location DSNXGRDS DSNXRTIM OFFSET7120(or
        OFFSET6B98) could happen for an SQL statement that has a '*' in
        the SELECT list and contains multiple outer joins with one of
        them as a nested outer join.

        To make the fix effective for a view that contains such an SQL
        statement, the view must be dropped and then created.

        To make this fix effective for a static application, it must 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
       DSNXOTDA  PM95677

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1      PM95677   DSNXOTDA

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOTDA

      LISTEND
 UI11909 COVER LETTER END


 UI12034 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM73905 -
        ****************************************************************
        * USERS AFFECTED: DB2 9 for z/OS, DB2 10 for z/OS, and         *
        *                 DB2 11 for z/OS users who may run a mass     *
        *                 delete operation.                            *
        ****************************************************************
        * PROBLEM DESCRIPTION: Deadlock between RTS daemon and an      *
        *                      application doing a mass delete may     *
        *                      occur when the application accesses     *
        *                      SYSTABLESPACESTATS or                   *
        *                      SYSINDEXSPACESTATS table in descending  *
        *                      OBID order.                             *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        A deadlock between RTS daemon and an application doing a mass
        delete operation occurs when the application is accessing
        SYSIBM.SYSTABLESPACESTATS or SYSIBM.SYSINDEXSPACESTATS
        table in descending OBID order while the
        RTS daemon accesses the tables in ascending order.

        DB2 is updated to avoid deadlock situations between RTS daemon
        and applications with mass delete operations.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM73905
    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  PM73905
       DSNIRTSU  PM73905
       DSNIRTSX  PM73905

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM73905   DSNICMT2 DSNIRTSU DSNIRTSX

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNICMT2
       DSNIRTSU
       DSNIRTSX
1
      LISTEND
 UI12034 COVER LETTER END


 UI12048 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM96307 -
        ****************************************************************
        * USERS AFFECTED: All DB2 users.                               *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C90101                     *
        *                      in DSNIZLDR ERQUAL5002                  *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        DB2 crashes for some reason while a LOAD LOG YES utility is
        running on a compressed table space. The crash hits a timing
        window in the LOAD utility and causes DB2 to lose track of the
        high formatted page number during restart. After restart, DB2
        fails to read a dictionary page when it detects that the page
        number is higher than the high formatted page number recorded
        in the VSAM catalog.
        DB2 has been fixed to preserve the high formatted page number
        across DB2 restart and avoid the abend after restart.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM96307
    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  PM96307
       DSNB1LDA  PM96307
       DSNB1OPP  PM96307

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM96307   DSNB1DRA DSNB1LDA DSNB1OPP

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNB1DRA
       DSNB1LDA
       DSNB1OPP

      LISTEND
 UI12048 COVER LETTER END


 UI12050 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM98429 -
        ****************************************************************
        * USERS AFFECTED: DB2 10 for z/OS (CM and NFM) and DB2 11 for  *
        *                 z/OS users of compressed table spaces and    *
1       *                 replication                                  *
        ****************************************************************
        * PROBLEM DESCRIPTION: This APAR implements the following      *
        *                      enhancements:                           *
        *                                                              *
        *                      (1). DB2 10 (CM and NFM) and DB2 11:    *
        *                           Allow IFI 306 (for QRep) to be     *
        *                           able to decompress compressed logs *
        *                           for user table spaces that are in  *
        *                           group buffer pool RECOVER-pending  *
        *                           status (GRECP)                     *
        *                                                              *
        *                      (2). DB2 10 (NFM) and DB2 11:           *
        *                           For the purposes of replication    *
        *                           to a second site via peer-to-peer  *
        *                           remote copy (PPRC), allow          *
        *                           compress-on-insert dictionary      *
        *                           pages (built starting in DB2 10    *
        *                           NFM by SQL INSERT or online LOAD   *
        *                           utility) to be written to DASD     *
        *                           as soon as the pages are built     *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        (1)

        Today, QREP Capture sends requests to IFI 306 for decompressed
        DB2 log data. For compressed tables, IFI 306 needs to access
        compression dictionaries to decompress log records before
        returning log data to QREP.

        Prior to this APAR, for pagesets or partitions that are in GRECP
        state, DB2 does not allow IFI 306 to access dictionary pages.
        The enhancement in this APAR is to allow access in such case.

        The reason is that, once a dictionary is built and written to
        DASD, it will not be updated during SQL mainline operations and
        there should be no updates on dictionary pages. So it would be
        safe for IFI 306 to access compression dictionaries even for
        table spaces that are in GRECP state (provided that the catalog
        or directory objects in databases DSNDB01 and DSNDB06 are not in
        any restrictive state).

        (2)

        DB2 10 NFM introduced the new compress-on-insert function which
        allows a compression dictionary to be built by SQL insert or by
        online LOAD utility. In a data sharing environment, the
        compress-on-insert dictionary pages are only written to group
        buffer pool after the dictionary is built.

        In order to allow compress-on-insert dictionary pages to be
        replicated to a second site via PPRC, in data sharing DB2 needs
        to be enhanced to write out compress-on-insert dictionary pages
        from group buffer pool to DASD immediately.
        DB2 code has been enhanced as follows:
1
        (1) Allow QREP to access compression dictionaries from table
        spaces that are in GRECP state, if the catalog and directory
        objects (in databases DSNDB01 and DSNDB06) are not in any
        restrictive state.

        (2) For the purposes of replication to a second site via PPRC,
        in a data sharing system, write out compress-on-insert
        dictionary pages from group buffer pool to DASD immediately.

        Additional keywords: IFCID306
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM98429
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNB1CLM  PM98429
       DSNB1OPP  PM98429
       DSNIDBCO  PM98429
       DSNIDBCQ  PM98429
       DSNISMRT  PM98429
       DSNIZLDL  PM98429

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM98429   DSNB1CLM DSNB1OPP DSNIDBCO DSNIDBCQ DSNISMRT DSNIZLDL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNB1CLM
       DSNB1OPP
       DSNIDBCO
       DSNIDBCQ
       DSNISMRT
       DSNIZLDL

      LISTEND
 UI12050 COVER LETTER END


 UI12055 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM96860 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users using   *
        *                 data sharing system                          *
        ****************************************************************
        * PROBLEM DESCRIPTION: Index page regression caused by down    *
        *                      level page written to GBP during DB2    *
        *                      restart REDO phase.                     *
        *                                                              *
        *                      ABND04E RC00C90206 LOC=DSNIDM           *
        *                      .DSNIDIFS ERQUAL5007 or other abends    *
        *                      caused by index page regression.        *
1       *                                                              *
        *                      CHECK INDEX utility also reports error. *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        In data sharing system, during DB2 restart REDO phase, index
        page could be marked as dirty when there is no need to apply
        the log record on this page. This results in potential
        index page regression, if another DB2 member also modifies
        the same index page.
        DB2 code has been fixed to avoid marking index page dirty
        if there is no need to apply the log record on this page
        during DB2 restart REDO phase.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM96860
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNKUNR2  PM96860

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM96860   DSNKUNR2

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNKUNR2

      LISTEND
 UI12055 COVER LETTER END


 UI12103 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM85857 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS users of ALTER TABLE ADD    *
        *                 PARTITION and users of Classic Partitioned   *
        *                 Table Spaces and Partition-by-Range          *
        *                 Universal Table Spaces (PBR UTS)             *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C90101 in DSNIDBHK with    *
        *                      ERQUAL500A during rollback of an ALTER  *
        *                      TABLE ADD PARTITION followed by DB2     *
        *                      coming down                             *
        *                                                              *
        *                      ABEND04E RC00C90101 in DSNIDBEL with    *
        *                      ERQUAL5221 during rollback of an ALTER  *
        *                      TABLE ADD PARTITION                     *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        During rollback of an ALTER TABLE ADD PARTITION, the following
        abends may be encountered when processing a table from Classic
1       partitioned table space or Partitioned-by-Range Universal Table
        Space (PBR UTS):

        ABEND04E RC00C90101 in DSNIDBHK with ERQUAL500A and DB2 going
        down (crash)
         - encountered by the receiving member of a notify message

        ABEND04E RC00C90101 in DSNIDBEL with ERQUAL5221
         - encountered by the sending member or the member where the
           ALTER TABLE ADD PARTITION is executing

        In both abends, the total number of partitions is less than the
        high partition range of an entry in an internal DBET control
        block.

        During processing of the ALTER to add a new partition, the new
        partition can be placed in extend-in-progress such that an
        entry for this new partition will be added in the DBET control
        block.

        However, further investigation shows that DBET is not properly
        cleaning up during rollback such that this newly added entry
        is left in the DBET control block.  As a result, sanity checks
        done later on to make sure that the entries in the DBET control
        block are correct will fail.
        DB2 has been modified to correctly clean up during rollback of
        an ALTER TABLE ADD PARTITION.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM85857
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNIDBDF  PM85857
       DSNIDBEL  PM85857
       DSNIDBGN  PM85857
       DSNIDBHK  PM85857
       DSNIDBMC  PM85857

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM85857   DSNIDBDF DSNIDBEL DSNIDBGN DSNIDBHK DSNIDBMC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIDBDF
       DSNIDBEL
       DSNIDBGN
       DSNIDBHK
       DSNIDBMC

      LISTEND
 UI12103 COVER LETTER END


1UI12184 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM99707 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 data sharing.               *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C202AA in DSNB1PER         *
        *                      during page set physical open.          *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Physical open of a page set may fail due to multiple Page Set
        Blocks (PBs) existing for the same page set. The DB2 restart
        code incorrectly calculates the user suffix area length for
        non-partitioned page sets, which may result in a new PB being
        built at end restart to replace one which was created earlier.
        If opens are driven under both PBs, the second open will fail
        due to an incompatible page set P-lock request.
        DB2 restart logic is changed to correctly calculate the user
        suffix area length for non-partitioned page sets, to avoid
        the P-locking failure.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM99707
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNIRCSB  PM99707

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM99707   DSNIRCSB

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIRCSB

      LISTEND
 UI12184 COVER LETTER END


 UI12197 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM96181 -
        ****************************************************************
        * USERS AFFECTED: All users of -ACCESS DB command on DB2 10    *
        *                 and 11 for z/OS                              *
        ****************************************************************
        * PROBLEM DESCRIPTION: There are 2 problems.                   *
        *                                                              *
        *                      1. DSNI048I message is missing when     *
        *                         -ACCESS DB is issued  with           *
        *                         MODE(NGBPDEP) and group bufferpool   *
        *                         dependency cannot be removed.        *
        *                                                              *
1       *                      2. Subsystem termination may occur when *
        *                         -CANCEL THD is issued against a DB2  *
        *                         command executing -ACCESS DB         *
        *                         MODE(OPEN).                          *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        1. When -ACCESS DB MODE(NGBPDEP) is issued and a given
           internal request to remove the group bufferpool dependency
           fails with a RC4, DB2 will incorrectly interpret that code
           and fail to issue the required I048 message.

        2. When a -CANCEL THD command is issued agaist a DB2 command
           executing -ACCESS DB MODE(OPEN), there is a window where
           recovery may not be properly set up, causing a subsystem
           termination.
        1. Correct DB2 code to externalize the DSNI048I message.

        2. Correct DB2 logic to properly reset the recovery environment
           for child tasks of the -ACCESS DB command after a cancel.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM96181
    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  PM96181

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM96181   DSNILSTS

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNILSTS

      LISTEND
 UI12197 COVER LETTER END


 UI12219 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM94651 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS , DB2 10 for z/OS and DB2 *
        *                 11 for z/OS users of COPY SHRLEVEL CHANGE    *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C200B0 DSNB1REL + x'0E1A'  *
        *                      during COPY FULL NO SHRLEVEL CHANGE on  *
        *                      a LOB table space.                      *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available.         *
        ****************************************************************
        User ran a COPY FULL NO SHRLEVEL CHANGE on a LOB table space.
        On some occasions, the job abended with ABEND04E RC00C200B0 at
1       DSNB1REL OFFSET0E1A because the COPY utility lost addressability
        to a buffer containing a space map page that it was trying to
        release.

        Similar problems can also happen for non LOB table spaces.
        COPY utility has been changed to track the buffer address of
        space map pages correctly.

        Additional keyword: Incremental
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM94651
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUBALS  PM94651
       DSNUBASA  PM94651
       DSNUBASP  PM94651

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM94651   DSNUBALS DSNUBASA DSNUBASP

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUBALS
       DSNUBASA
       DSNUBASP

      LISTEND
 UI12219 COVER LETTER END


 UI12259 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM98427 -
        ****************************************************************
        * USERS AFFECTED: DB2 V9 users with UK92093 applied.           *
        *                 DB2 V10 users with UK92092 applied.          *
        *                 All DB2 V11 users.                           *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND978 and DB2 abnormal termination   *
        *                      RC00D94001.                             *
        *                                                              *
        *                      Abend is most likely to occur after a   *
        *                      cancel of a LOAD or REORG utility with  *
        *                      the PREFORMAT option specified.         *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        PM80265 modified the I/O abend recovery logic to allow for the
        presence of an I/O error block (MMRBE) even if the I/O error
        flag was not on.  However, the pointer to this block in the
        MMRB is a shared field which Media Manager may store a CI number
        into during a preformat request.  Therefore a canceled preformat
1       may cause the recovery routine to misinterpret a CI number as a
        block pointer, resulting in an abend 978 when an attempt is made
        to free that block.  Since this abend happens during abort
        processing, it brings down DB2.
        The I/O recovery code has been modified to remove the change
        made by PM80265, for the preformat case only.  Preformat is the
        only case where Media Manager may store something into the field
        used to store the error block pointer, and preformat is not
        subject to the problem fixed by PM80265 (the presence of an
        I/O block for a "related" I/O error).
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM98427
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNB1IOR  PM98427

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM98427   DSNB1IOR

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNB1IOR

      LISTEND
 UI12259 COVER LETTER END


 UI12392 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM96585 -
        ****************************************************************
        * USERS AFFECTED: All DB2 V10 and V11 users.                   *
        ****************************************************************
        * PROBLEM DESCRIPTION: (1) Abend0c4 in the FRR of super        *
        *                      recovery module DSNSRSUP when r15 is    *
        *                      checked without being set.              *
        *                      (2) Abend0c4 in the super recovery      *
        *                      module routine STKVRFY while trying     *
        *                      to validate an active ATBLNTRY.         *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        (1) ABENDS0C4 in the FRR of super recovery module DSNSRSUP when
        an attempt is made to free the vsab latch but it is not held.
        The outcome of the latch check when it is made is placed in R15.
        Since the prior logic indicated the vsab latch could not be
        held, the actual check was never made and R15 contained residual
        data.  That data implied the vsab latch was held and the FRR
        then abended attempting to free that latch.
        (2) ABENDS0C4 in the super recovery module DSNSRSUP when two
        processes were operating on the same ATBLNTRY at the same time.
        A thread abended while EBSMC was set, driving it into DSNSRSUP
1       recovery where part of the flow is to verify all stack table
        entries.  While this process was stepping through the entries
        and validating the SKB, DSNSPURS was purging the SKB from a
        normally terminating thread.  This happened to be the thread
        which owned that ATBLNTRY and so cleared the entry and
        freemained the SKB, resulting in the DSNSRSUP abend0c4.
        (1) The check for vsab latch ownership results will only be done
        if the ownership is actually tested.
        (2) The order of instructions to invalidate a stack ATBL entry,
        was changed to adhere to same protocol used everywhere else.
        The routine to have abending threads attempt to validate all
        DB2 stack entries and invalidate those entries suspected of
        being bad, can not obtain proper serialization.  This code is
        removed and only this threads stack will be verified.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM96585
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNSPURS  PM96585
       DSNSRSUP  PM96585

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM96585   DSNSPURS DSNSRSUP

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNSPURS
       DSNSRSUP

      LISTEND
 UI12392 COVER LETTER END


 UI12398 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM96918 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 10 and DB2 11 for z/OS      *
        *                 who use spatial indexes.                     *
        ****************************************************************
        * PROBLEM DESCRIPTION: Incorrect output may occur if DB2       *
        *                      chooses spatial indexes                 *
        *                      to access an inner table in             *
        *                      an outer join query block.              *
        *                                                              *
        *                      SQLSPATIAL SQLOUTERJOIN                 *
        *                      SQLFULLJOIN SQLOUTER                    *
        *                      SQLFULL SQLLEFTJOIN SQLLEFT             *
        *                      SQLRIGHTJOIN SQLRIGHT                   *
        *                      INCORROUT SQLINCORROUT                  *
        *                      SQLINCORR DB2INCORR/K                   *
        ****************************************************************
1       * RECOMMENDATION:                                              *
        ****************************************************************
        Incorrect output may occur if DB2 chooses a spatial index
        to access an inner table in an outer join query block.

        The incorrect output occurs because DB2 cannot support
        spatial indexes to be used in an outer join query
        block.
        The incorrect output is fixed by not using spatial indexes
        on the tables that will be padded with NULL in an outer
        join query block.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM96918
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        See PM96918 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM96918 corrects a problem where more rows may be returned when
        a spatial index is used on the inner table of an 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
       DSNXODF   PM96918

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM96918   DSNXODF

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXODF

      LISTEND
 UI12398 COVER LETTER END


 UI12614 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM98157 -
        ****************************************************************
        * USERS AFFECTED: DB2 users using buffer pools defined with:   *
        *                   - VPSIZE less than 100                     *
        *                   - VDWQT(0,0)                               *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C90101 ERQUAL5002 in       *
        *                      DSNKIXDB during CREATE INDEX or         *
        *                      REBUILD INDEX.                          *
        *                                                              *
1       *                      Other symptoms of lost data updates,    *
        *                      including:                              *
        *                       - Incorrect output, INCORROUT.         *
        *                       - ABEND04E RC00C90101, RC00C90102,     *
        *                         RC00C90105, or RC00C902xx in         *
        *                         various CSECTs.                      *
        *                       - Data/index inconsistencies reported  *
        *                         by the CHECK INDEX utility.          *
        *                       - Page regression reported by the      *
        *                         DSN1LOGP utility.                    *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        For a buffer pool smaller than 100 buffers, with the VDWQT
        attribute set to (0,0), the DASD write logic will incorrectly
        set the number of pages to write to zero, effectively making
        sure that no updates will ever be written.  This results in
        various "broken data" symptoms.
        The DASD write logic has been fixed to no longer skip writes
        when the buffer pool is smaller than 100 buffers and has VDWQT
        set to (0,0).
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM98157
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNB5COM  PM98157

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM98157   DSNB5COM

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNB5COM

      LISTEND
 UI12614 COVER LETTER END


 UI12639 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM98942 -
        ****************************************************************
        * USERS AFFECTED: All DB2 users.                               *
        ****************************************************************
        * PROBLEM DESCRIPTION: After receiving message:                *
        *                      DSNT500I                                *
        *                       =D2T1 DSNGEDLC RESOURCE UNAVAILABLE    *
        *                                 REASON 00C90089              *
        *                                 TYPE 00000602                *
        *                                 NAME EDM DBD SPACE           *
        *                      The following abend was received:       *
        *                      ABEND04E in DSNIOPPS 500A RC00C90101.   *
1       ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        System received ABEND04E in DSNIOPPS ERQUAL500A RC00C90101.
        The console had several messages
        DSNT500I  =D2T1 DSNGEDLC RESOURCE UNAVAILABLE
                   REASON 00C90089
                   TYPE 00000602
                   NAME EDM DBD SPACE

        Running REPAIR DBD TEST on the database would run clean on one
        member but show errors on the member that got the full condition
        and the abend.  After stopping and starting DB2 on the member
        that got the errors REPAIR DBD TEST would run clean.
        The MSGDSNT500I RC00C90089 or an EDM DBD POOL full occurred
        while a DBD was being loaded.  This caused the DBD to be
        partially puffed in storage and made available for use on that
        member.  This caused the reported abend and message and could
        also cause other unpredictable results.  Once the DBD was
        partially puffed DB2 would need to be stopped and started on the
        member that has the problem to correct the problem.  The code
        has been updated to detect when a problem has occurred while a
        DBD is being loaded and to not leave a partially puffed DBD in
        storage.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM98942
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNGECHK  PM98942
       DSNGEDLC  PM98942

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM98942   DSNGECHK DSNGEDLC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNGECHK
       DSNGEDLC

      LISTEND
 UI12639 COVER LETTER END


 UI12644 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM92701 -
        ****************************************************************
        * USERS AFFECTED: All DB2 V9 or V10 z/OS users.                *
        ****************************************************************
        * PROBLEM DESCRIPTION: An ABEND04E RC00E20016 may occur in     *
        *                      module DSNSVSTK after a CICS userid is  *
        *                      repeatedly rejected with RC00F30054 or  *
1       *                      RC00F30058.  The leaked storage is the  *
        *                      DB2 stack storage which contains the    *
        *                      eye-catcher '3ID80' which is the save   *
        *                      area for module DSN3ID80.               *
        *                      This storage is in the CICS region.     *
        *                      The CICS region may also receive an     *
        *                      ABEND878.                               *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An ABEND04E RC00E20016 may occur in module DSNSVSTK after
        many CICS calls to DB2 SIGNON are rejected by the DB2 Signon
        authorization exit.
        Each CICS call to DB2 SIGNON receives a RC00F30058
        which means the userid is rejected by the authorization
        exit.  CICS makes a TERMINATE call to to DB2.
        That TERMINATE call causes DSN3ID80 to set RC00F30054
        and DSN3ID80 does not clean up its DB2 stack entry.
        Module DSN3ID80 has been updated to avoid the ABEND04E
        RC00E20016 and ABEND878 in the application address space.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM92701
    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  PM92701

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM92701   DSN3ID80

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSN3ID80

      LISTEND
 UI12644 COVER LETTER END


 UI12646 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM94155 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users with               *
        *                 PM73034 (UK94806) using LOAD FORMAT          *
        *                 SPANNED YES.                                 *
        *                 All DB2 11 for z/OS users of LOAD FORMAT     *
        *                 SPANNED YES.                                 *
        ****************************************************************
        * PROBLEM DESCRIPTION: On DB2 10 for z/OS with PM73034         *
        *                      (UK94806) and DB2 11 for z/OS,          *
        *                      LOAD FORMAT SPANNED YES with an XML     *
        *                      field only loaded the first record      *
        *                      from SYSREC.                            *
1       *                      Also, LOAD FORMAT SPANNED YES did       *
        *                      not process NULLIF on a LOB field       *
        *                      correctly, resulting in no rows         *
        *                      loaded or abend ABEND0C4 RC00000004     *
        *                      at DSNURWRF +x'1052'.                   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        On DB2 10 for z/OS with PM73034 (UK94806) and DB2 11 for z/OS,
        LOAD FORMAT SPANNED YES incorrectly indexed to an XML field
        for all records after the first record in SYSREC.  Only the
        first record was processed correctly and loaded into the table.
        All subsequent records were discarded.


        LOAD FORMAT SPANNED YES did not process NULLIF on a LOB field
        correctly, resulting in no rows loaded or abend
        ABENDS0C4 DSNURWRF OFFSET1052 RC4.  This occurred when the
        NULLIF referred to a field or location which was not immediately
        before the LOB field in the VBS logical record.
        Modified LOAD FORMAT SPANNED YES functionality to correctly
        index XML fields for the case above.
        Modified LOAD FORMAT SPANNED YES functionality to correctly
        process NULLIF for LOB fields as described above.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM94155
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNURWRF  PM94155

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM94155   DSNURWRF

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNURWRF

      LISTEND
 UI12646 COVER LETTER END


 UI12648 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PI04942 -
        ****************************************************************
        * USERS AFFECTED: DB2 10 and 11 for z/OS users who performed   *
        *                 insert operations to segmented tablespaces   *
        *                 (including UTS type) with large volumns of   *
        *                 data on the table.                           *
        ****************************************************************
        * PROBLEM DESCRIPTION: Insert performance seriously suffered   *
        *                      which observed an average of 40K-60K    *
1       *                      numbers of getpages per insert.         *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When an object table contains larger quantity of data rows under
        a segmented table space (including a UTS table space), DB2
        mistakenly calculated a wrong segment number due to the use of
        smaller integer fields.  This wrong segment calculation would
        degrade the overall insert performance.
        DB2 code is fixed to adopt long integer fields to calculate
        the segment number.

        Additional keywords: PERFM
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PI04942
    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  PI04942
       DSNIDILS  PI04942
       DSNIDLDS  PI04942
       DSNIDLDU  PI04942
       DSNIDLEO  PI04942
       DSNIFOD   PI04942
       DSNILAST  PI04942
       DSNILPG   PI04942
       DSNINXPG  PI04942
       DSNINXTP  PI04942
       DSNIPREP  PI04942
       DSNIRELF  PI04942
       DSNIRSET  PI04942
       DSNISEGD  PI04942
       DSNISEGF  PI04942
       DSNISGNS  PI04942
       DSNISGPI  PI04942
       DSNISGRT  PI04942
       DSNISGSC  PI04942
       DSNISGSS  PI04942
       DSNISGSU  PI04942
       DSNISHPI  PI04942
       DSNISNPG  PI04942
       DSNISRID  PI04942
       DSNISRTW  PI04942
       DSNISUPI  PI04942
       DSNITLPE  PI04942
       DSNITNPG  PI04942
       DSNIWLPG  PI04942
       DSNIWNRF  PI04942
       DSNIWSET  PI04942
       DSNIWTTD  PI04942
       DSNIZLDL  PI04942

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PI04942   DSNICMT2 DSNIDILS DSNIDLDS DSNIDLDU DSNIDLEO DSNIFOD
1                DSNILAST DSNILPG  DSNINXPG DSNINXTP DSNIPREP DSNIRELF
                 DSNIRSET DSNISEGD DSNISEGF DSNISGNS DSNISGPI DSNISGRT
                 DSNISGSC DSNISGSS DSNISGSU DSNISHPI DSNISNPG DSNISRID
                 DSNISRTW DSNISUPI DSNITLPE DSNITNPG DSNIWLPG DSNIWNRF
                 DSNIWSET DSNIWTTD DSNIZLDL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNICMT2
       DSNIDILS
       DSNIDLDS
       DSNIDLDU
       DSNIDLEO
       DSNIFOD
       DSNILAST
       DSNILPG
       DSNINXPG
       DSNINXTP
       DSNIPREP
       DSNIRELF
       DSNIRSET
       DSNISEGD
       DSNISEGF
       DSNISGNS
       DSNISGPI
       DSNISGRT
       DSNISGSC
       DSNISGSS
       DSNISGSU
       DSNISHPI
       DSNISNPG
       DSNISRID
       DSNISRTW
       DSNISUPI
       DSNITLPE
       DSNITNPG
       DSNIWLPG
       DSNIWNRF
       DSNIWSET
       DSNIWTTD
       DSNIZLDL

      LISTEND
 UI12648 COVER LETTER END


 UI12699 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PI04789 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users *
        *                 using varying length, NOT PADDED indexes.    *
        ****************************************************************
        * PROBLEM DESCRIPTION: Multiple symptoms may occur while       *
        *                      populating varying length, NOT PADDED   *
1       *                      index, after running REORG TABLESPACE,  *
        *                      or during LOAD REPLACE or SQL INSERT:   *
        *                         - ABEND0C4 RC00000038 DSNKINSL       *
        *                         - ABEND0C4 RC0000003B DSNKISPL       *
        *                         - ABEND04E RC00E2000F DSNSVSFB       *
        *                         - ABEND04E RC00C200C9 DSNB1OFA       *
        *                         - ABEND04E RC00C90105 DSNKINSL       *
        *                                               ERQUAL0D43     *
        *                         - ABEND04E RC00C90101 DSNILGCL       *
        *                                               ERQUAL5004     *
        *                         - Storage overlay                    *
        *                         - Data corruption                    *
        *                         - Bring DB2 subsystem down           *
        *                         - other abends/symptoms              *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        In certain cases, a REORG TABLESPACE or LOAD REPLACE can leave
        pseudo deleted keys in index leaf pages. If the same key value
        is later inserted in to that leaf page, DB2 should physically
        remove the existing, duplicate pseudo deleted key, before
        inserting the new key value.  The position for insert should be
        recalculated, after the old key is physically removed, and
        before the insert.

        Since the index page had a PGLOGRBA value of zero, having been
        created by the REORG TABLESPACE or LOAD REPLACE, the position
        on the page was not being recalculated.  This caused the new
        key value to overlay surrounding keys and sometimes surrounding
        pages (depending on size).

        Additional keywords: DB2OVRLAY/K DB2TERM DB2ABTERM RC00D10231
        DB2 has been modified to correctly reposition on the index page
        when duplicate pseudo deleted keys are physically removed.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PI04789
    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  PI04789

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PI04789   DSNKINSL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNKINSL

      LISTEND
 UI12699 COVER LETTER END


 UI12795 COVER LETTER START
1   PROBLEM DESCRIPTION(S):
      PM96639 -
        ****************************************************************
        * USERS AFFECTED: All DB2 users with migrated data sets.       *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C4 RC00000038 in DSNB1TMR         *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        A rare timing window exists between an open operation and a
        data set recall process. When the open operation is cancelled
        after the recall is complete, the recall request block (RSTPARM)
        is no longer available. The open operation incorrectly assumes
        that the recall process has not started and sets a flag in
        RSTPARM to indicate its cancelled status, causing an one bit
        storage overlay. The results of the overlay are unpredictable,
        but one observed symptom is an ABEND0C4 in DSNB1TMR.
        DB2 has been fixed to eliminate setting and checking the
        cancelled status flag in the RSTPARM block. This closes the
        timing window between the open and recall tasks and allows the
        recall task to process the recall request independently
        without being influenced by the requester's cancelled status.
        When the open task is cancelled, it will go through its
        recovery without overlaying storage in case the recall task
        completes first.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM96639
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNB1OPP  PM96639
       DSNB1OPS  PM96639
       DSNB1RST  PM96639

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM96639   DSNB1OPP DSNB1OPS DSNB1RST

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNB1OPP
       DSNB1OPS
       DSNB1RST

      LISTEND
 UI12795 COVER LETTER END


 UI12801 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM97759 -
        ****************************************************************
        * USERS AFFECTED: DB2 data sharing users, with table spaces    *
        *                 or indexes defined as GBPCACHE NONE or       *
1       *                 group bufferpools defined as GBPCACHE(NO).   *
        ****************************************************************
        * PROBLEM DESCRIPTION: Page regression in data sharing,        *
        *                      resulting in any of the following:      *
        *                       - 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:                                              *
        ****************************************************************
        When an application updates pages in a GBP-dependent table space
        or index, which is either defined as GBPCACHE NONE or uses a
        group buffer pool defined as GBPCACHE(NO), the updates are
        written to DASD at commit.  The writes are done asynchronously
        by a GBP write engine, and the commit processing must wait for
        the writes to complete.  However, for the case where all of the
        GBP write engines are busy and the request has to be queued
        until one becomes available, the commit processing may not wait.
        Therefore the locks on the data can be released before the
        writes are done, and another member can see or update down-
        level data, resulting in various "broken data" problems.
        The asynchronous write scheduling code has been fixed to make
        sure that force-at-commit writes to DASD are flagged as 
"active"
 
        for the case where the request is queued awaiting an available
        GBP write engine.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM97759
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNB1CMU  PM97759
       DSNB1TPL  PM97759

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM97759   DSNB1CMU DSNB1TPL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNB1CMU
       DSNB1TPL

      LISTEND
 UI12801 COVER LETTER END


 UI12977 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM95545 -
1       ****************************************************************
        * USERS AFFECTED: All DB2 users of the -DISPLAY DATABASE       *
        *                 command with the LIMIT and LOCKS keywords.   *
        ****************************************************************
        * PROBLEM DESCRIPTION: The -DISPLAY DATABASE command invoked   *
        *                      with the LIMIT and LOCKS keywords could *
        *                      generate an ABEND04E RC00F9000C in      *
        *                      DSN9SCNP.                               *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The -DISPLAY DATABASE command invoked with the LIMIT and LOCKS
        keywords generated an ABEND04E RC00F9000C in DSN9SCNP when
        generating a continuation line within the displaying of a
        partitioned table space or index.
        Changed the -DISPLAY DATABASE command to assure that sufficient
        reserved lines are available in the MWTO structure when
        generating a continuation message when the LOCKS keyword is
        used.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM95545
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNTDMUL  PM95545

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM95545   DSNTDMUL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNTDMUL

      LISTEND
 UI12977 COVER LETTER END


 UI13035 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM97952 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 and 11 for z/OS users of pureXML. *
        ****************************************************************
        * PROBLEM DESCRIPTION: XMLTABLE is often used for shredding    *
        *                      XML documents into different columns    *
        *                      based on diverging XPATH patterns       *
        *                      (different at path or leaf level); A    *
        *                      special usage of XMLTABLE is to have    *
        *                      almost identical XPATHs (path patterns  *
        *                      are exactly identical while only differ *
        *                      in the right-hand-side values of a      *
        *                      predicate) for different columns.       *
        *                                                              *
1       *                      In the current XMLTable implementation, *
        *                      each column XPATH evaluation involves a *
        *                      scan, wherein the performance issue     *
        *                      arise - it could be very time consuming *
        *                      when document is big and the number of  *
        *                      columns is big.                         *
        ****************************************************************
        * RECOMMENDATION: This is the preconditioning APAR for         *
        *                 performance enhancement of XMLTABLE function *
        *                 with special column XPATH pattern.           *
        *                                                              *
        *                 Also, the fast scan algorithm is enabled for *
        *                 XPATH that has function fn:string-length().  *
        ****************************************************************
        For the special column XPATH pattern (paths
        share the identical pattern except the
        predicate values, which correspond to
        different column names), we manage to merge
        such paths into one with predicate values
        aggregated in an array. We then use one scan
        to get the results for many columns. This
        way, we may greatly improve the performance
        of XMLTABLE with such column XPATH pattern.

        For example, columns C3, C4 and C5 of Q1 will be
        merged together to be evaluated in one scan.

        Q1:

        SELECT X.* FROM T1,
        XMLTABLE('/a/b' PASSING T1.ODOC
        COLUMNS
        C1 INT          PATH 'c',
        C2 VARCHAR(20)  PATH 'd/e',
        C3 INT          PATH 'g[@h="a"]/@k',
        C4 INT          PATH 'g[@h="b"]/@k',
        C5 VARCHAR(10)  PATH 'g[@h="c"]/@k',
        C6 VARCHAR(20)  PATH 'g/x') X;
        PM97952 is a pre-conditioning APAR that includes changes to
        enhance the performance of XMLTABLE function whose column XPATHs
        share a special (column name, predicate value pair) pattern. The
        enabling apar is PM98160.

        Additional Keyword: SQLXML XMLALL XMLTABLE
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM97952
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      MULTSYS:
        See PM97952 APAR/PTF text for additional information.

        PM97952 is a pre-conditioning APAR that includes changes to
        enhance XMLTABLE performance which will be enabled via APAR
        PM98160 later. At this time, all changes are transparent
        to the user. In a data sharing group, this pre-conditioning
1       APAR should be applied to all members before the enabling
        APAR is applied to any member. The performance enhancement is
        not enabled until the enabling APAR PM98160 is applied.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNNQDTM  PM97952
       DSNNQIV   PM97952
       DSNNQOPM  PM97952
       DSNNQOPN  PM97952
       DSNNQOPR  PM97952
       DSNNQOPS  PM97952
       DSNNQRES  PM97952
       DSNNQXCA  PM97952

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM97952   DSNNQDTM DSNNQIV  DSNNQOPM DSNNQOPN DSNNQOPR DSNNQOPS
                 DSNNQRES DSNNQXCA

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNNQDTM
       DSNNQIV
       DSNNQOPM
       DSNNQOPN
       DSNNQOPR
       DSNNQOPS
       DSNNQRES
       DSNNQXCA

      LISTEND
 UI13035 COVER LETTER END


 UI13153 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM97867 -
        ****************************************************************
        * USERS AFFECTED: All DB2 V10 for z/OS users of applications   *
        *                 that access Universal Table space (UTS)      *
        *                 with a data pattern of insert and            *
        *                 delete.                                      *
        ****************************************************************
        * PROBLEM DESCRIPTION: An application that accesses            *
        *                      Universal Table Space (UTS) could       *
        *                      result in high get page count if the    *
        *                      data accessing pattern consists of      *
        *                      inserts and deletes.                    *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When deleted space distributes through the table space,
        the subsequent insert process could result in high get page
        count. This is due to the false lead threshold that was
        increased to improve space reuse within the candidate segment
        or during the exhaustive search prior to physical extend.
1       However, the extra page search does not fit for the situation
        where the data page has unusable free space. As a result, the
        get page count would increase by visiting more pages for each
        search step.
        DB2 code was changed to limit the threshold increase to
        DSNDBD01 object only.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM97867
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNISUPI  PM97867

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM97867   DSNISUPI

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNISUPI

      LISTEND
 UI13153 COVER LETTER END


 UI13278 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM96415 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS, DB2 10 for z/OS and DB2  *
        *                 11 for z/OS utility users of RUNSTATS        *
        *                 TABLESPACE HISTOGRAM                         *
        ****************************************************************
        * PROBLEM DESCRIPTION: RUNSTATS TABLESPACE HISTOGRAM abends    *
        *                      with ABEND0C4 at DSNUSIDX +x'D95C'      *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        RUNSTATS TABLESPACE HISTOGRAM abended with ABENDS0C4 at DSNUSIDX
        OFFSETD95C.  The error occurred during the initialization of the
        HISTOGRAM control blocks.  When calculating the offset of the
        data portion of a nullable decimal column for one of the
        indexes, a wrong offset was used which resulted in 255 bytes
        overlaying already allocated storage.  The ABENDS0C4 resulted
        from this overlay.

        Additional Keywords: DB2OVRLAY DB2OVRLAY/K DB2OVRLAY/M
                             DB2OVRLAY/N
        RUNSTATS TABLESPACE HISTOGRAM code has been changed to correctly
        calculate the NULL byte in a key column.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM96415
    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
       DSNUSIDX  PM96415

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM96415   DSNUSIDX

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUSIDX

      LISTEND
 UI13278 COVER LETTER END


 UI13283 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM98842 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 10 and DB2 11               *
        *                 for z/OS users who have                      *
        *                 subsystem parameters STARJOIN=ENABLE         *
        *                 and EN_PJSJ=ON and are running               *
        *                 queries with DEGREE(ANY).                    *
        ****************************************************************
        * PROBLEM DESCRIPTION: Incorrect output with no rows found     *
        *                      may occur when DB2 is processing a      *
        *                      query bound or prepared with            *
        *                      DEGREE(ANY) when a parallel             *
        *                      pair-wise join plan is degenerated      *
        *                      to a sequential plan.                   *
        *                                                              *
        *                      SQLPAIRWISEJOIN PAIRWISE JOIN           *
        *                      SQLCPUP PARALLELISM                     *
        *                      INCORROUT SQLINCORROUT                  *
        *                      SQLINCORR DB2INCORR/K                   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Incorrect output with no rows found may occur when DB2 is
        processing a query bound or prepared with DEGREE(ANY) when
        a parallel pair-wise join plan is degenerated to a
        sequential plan.

        The problem occurs due to an internal bug in the pair-wise
        join processing.
        The problem described above is fixed by setting
        the internal threshold related to pair-wise join
        processing.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM98842
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
1     DB2BIND:
        See PM98842 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM98842 corrects an incorrect output problem with DEGREE(ANY)
        when a parallel pairwise join plan is degenerated to a
        sequential 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
       DSNXOSJX  PM98842

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM98842   DSNXOSJX

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOSJX

      LISTEND
 UI13283 COVER LETTER END


 UI13364 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM96082 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS      *
        *                 users of RECOVER TORBA or TOLOGPOINT.        *
        ****************************************************************
        * PROBLEM DESCRIPTION: DB2 11:                                 *
        *                      MSGDSNU809I during CHECK DATA of a      *
        *                      partition-by-growth (PBG) table space   *
        *                      following a RECOVER TOLOGPOINT using a  *
        *                      FLASHCOPY CONSISTENT image copy.        *
        *                                                              *
        *                      DB2 10:                                 *
        *                      Serviceability for RECOVER TOLOGPOINT   *
        *                      or TORBA.                               *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        DB2 11:
        Residual data was left in partitions of a PBG table space
        after being recovered by a RECOVER TOLOGPOINT to a point in
        time before those partitions were added and a FLASHCOPY
        CONSISTENT image copy was used as a base for recovery.
        A subsequent CHECK DATA issued DSNU809I - TABLE= tablename
        COLUMN= columnname IS MISSING IN INDEX indexname and ended with
        RC4.  When a FlashCopy image copy was used as the recovery
        base, the partitions added after the FLASHCOPY CONSISTENT was
1       taken were not emptied.  These partitions may also not be in the
        correct RBA or LRSN format, e.g., basic or extended RBA or LRSN
        format, if the format had changed after the recovery point.

        DB2 10:
        Serviceability for RECOVER TOLOGPOINT or TORBA.
        RECOVER code has been modified to correct the aforementioned
        problem.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM96082
    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  PM96082

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM96082   DSNUCALA

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUCALA

      LISTEND
 UI13364 COVER LETTER END


 UI13455 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM94906 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS, DB2 10 for z/OS, and DB2 *
        *                 11 for z/OS users of materialized query      *
        *                 table.                                       *
        ****************************************************************
        * PROBLEM DESCRIPTION: A SQLCODE20093 with reason code '09' is *
        *                      not issued when altering a base table   *
        *                      to a materialized query table directly  *
        *                      or indirectly referencing the same base *
        *                      table in the materialized query         *
        *                      definition fullselect.                  *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        A SQLCODE20093 with reason code '09' is not issued when altering
        a base table to a materialized query table directly or
        indirectly referencing the same base table in the materialized
        query definition fullselect. It is because when altering a base
        table to a materialized query table, DB2 does not properly
        validate the table(s) involved in the fullselect.

        Following is an example of such failing scenario:
        DROP TABLE TM1;

1       CREATE TABLE TM1
          (C1   INT,
           C2   CHAR(10) );
        COMMIT;

        * Directly referencing the same base table in the fullselect
        * A SQLCODE20093 with reason code '09' should be issued
        ALTER TABLE TM1 ADD MATERIALIZED QUERY
            (SELECT * FROM TM1)
            DATA INITIALLY DEFERRED REFRESH DEFERRED
            MAINTAINED BY SYSTEM
            ENABLE QUERY OPTIMIZATION
        ;

        * Or indirectly referencing the same base table in the
        * fullselect
        * A SQLCODE20093 with reason code '09' should be issued
        ALTER TABLE TM1 ADD MATERIALIZED QUERY
            (SELECT * FROM (SELECT * FROM TM1) TX
            )
            DATA INITIALLY DEFERRED REFRESH DEFERRED
            MAINTAINED BY SYSTEM
            ENABLE QUERY OPTIMIZATION
        ;
        DB2 is modified to properly validate the table(s) directly or
        indirectly referenced in the materialized query definition
        fullselect and issue a SQLCODE20093 with reason code '09'
        when a violation is detected.

        After applying this APAR, the existing MQT table that have
        been incorrectly created won't be fixed.

        Additional Keywords: SQLALTER SQLMQT SQLINCORR INCORROUT
                             SQLINCORROUT DB2INCORR/K SQLCODE20093
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM94906
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXIAST  PM94906

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM94906   DSNXIAST

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXIAST

      LISTEND
 UI13455 COVER LETTER END


 UI13461 COVER LETTER START
1   PROBLEM DESCRIPTION(S):
      PM98313 -
        ****************************************************************
        * USERS AFFECTED: All DB2 users of the packages                *
        ****************************************************************
        * PROBLEM DESCRIPTION: After a cancel, the latch DMCHASH       *
        *                      CLASS 25 in EDMKHASH block EDM HASH     *
        *                      TABLE FOR SKPTS is not released. This   *
        *                      caused many threads waiting for the     *
        *                      same latch to suspend. Eventually no    *
        *                      more threads can be processed and the   *
        *                      subsystem hangs.                        *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        DB2 error recovery does not unlatch class 25
        latch DMCHASH, which causes the above problem.

        Additional keywords: LC25 latch class 25
        DB2 code has been changed to unltach the latch class 25 after
        the thread execution is cancelled.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM98313
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNGENER  PM98313
       DSNGEPDL  PM98313
       DSNGEPLC  PM98313

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM98313   DSNGENER DSNGEPDL DSNGEPLC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNGENER
       DSNGEPDL
       DSNGEPLC

      LISTEND
 UI13461 COVER LETTER END


 UI13510 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PI05093 -
        ****************************************************************
        * USERS AFFECTED: All IRLM230 (HIR2230) users.                 *
        ****************************************************************
        * PROBLEM DESCRIPTION: After installing UK96959/PM89139, IRLM  *
        *                      may:                                    *
        *                                                              *
        *                      1. incorrectly issue DXR175E message    *
1       *                       indicating that below-the-bar private  *
        *                       storage has reached threshold value.   *
        *                                                              *
        *                      2. encounter S0C1 abend in various      *
        *                       offset in DXRRL400.                    *
        *                                                              *
        ****************************************************************
        * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
        ****************************************************************
        1. Below-the-bar private storage accounting:

           IRLM keeps track of all below-the-bar private storage in
        an accounting field.  When this below-the-bar accounting field
        reaches or exceeds the threshold value, message DXR175E will
        be issued on the console.

           When a new segment of below-the-bar private storage is
        obtained, its value is added into the accounting field.  When
        a free segment is compressed (FREEMAINed), its value is
        subtracted from the accounting field.

           For every lock control block (RHB/RLB/RHBL), there is an
        index block (RLBI), below-the-bar private storage, associated
        with above-the-bar RLB addresses.  Whenever the lock control
        block (RHB/RLB/RHBL) gets compressed, so does its associated
        RLBI block.  There is no existing logic to subtract the RLBI
        length after it gets compressed.

        2. New Extended-immediate facility instructions:

           In PM89139/UK96959, IRLM used several new immediate assembler
        instructions.  These new instructions are supported by the
        extended-immediate facility which exists in machine z9-109 and
        later.  For customer that runs on older machine (z890), these
        new immediate instructions cause abend S0C1 in IRLM storage
        manager code.

        GEN:
        KEYWORDS:

        *** END IMS KEYWORDS ***
        1. Below-the-bar private storage accounting:
           Code is added to subtract the length of the RLBI block from
        the accounting field whenever it gets compressed.

        2. S0C1 abend in storage manager:
           All new immediate instructions are replaced by equivalent
        assembler instructions.

    COMPONENT:  5695-16401-HIR2230
    APARS FIXED: PI05093
    SPECIAL CONDITIONS:
      COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
1      DXRRL0B0  PI05093
       DXRRL010  PI05093
       DXRRL040  PI05093
       DXRRL090  PI05093
       DXRRL1E0  PI05093
       DXRRL1H9  PI05093
       DXRRL1S0  PI05093
       DXRRL1S1  PI05093
       DXRRL120  PI05093
       DXRRL150  PI05093
       DXRRL160  PI05093
       DXRRL190  PI05093
       DXRRL2B0  PI05093
       DXRRL2R1  PI05093
       DXRRL2R2  PI05093
       DXRRL2R3  PI05093
       DXRRL2R4  PI05093
       DXRRL210  PI05093
       DXRRL211  PI05093
       DXRRL24B  PI05093
       DXRRL24F  PI05093
       DXRRL246  PI05093
       DXRRL247  PI05093
       DXRRL400  PI05093
       DXRRL401  PI05093

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PI05093   DXRRL0B0 DXRRL010 DXRRL040 DXRRL090 DXRRL1E0 DXRRL1H9
                 DXRRL1S0 DXRRL1S1 DXRRL120 DXRRL150 DXRRL160 DXRRL190
                 DXRRL2B0 DXRRL2R1 DXRRL2R2 DXRRL2R3 DXRRL2R4 DXRRL210
                 DXRRL211 DXRRL24B DXRRL24F DXRRL246 DXRRL247 DXRRL400
                 DXRRL401

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DXRRL0B0
       DXRRL010
       DXRRL040
       DXRRL090
       DXRRL1E0
       DXRRL1H9
       DXRRL1S0
       DXRRL1S1
       DXRRL120
       DXRRL150
       DXRRL160
       DXRRL190
       DXRRL2B0
       DXRRL2R1
       DXRRL2R2
       DXRRL2R3
       DXRRL2R4
       DXRRL210
       DXRRL211
       DXRRL24B
1      DXRRL24F
       DXRRL246
       DXRRL247
       DXRRL400
       DXRRL401

      LISTEND
 UI13510 COVER LETTER END


 UI13513 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM96981 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9, 10 and 11 for z/OS users of Mass  *
        *                 Delete to table in segmented table space     *
        *                 including universal table space.             *
        ****************************************************************
        * PROBLEM DESCRIPTION: Following symptoms are possible after   *
        *                      Mass Delete to a table in a segmented   *
        *                      table space                             *
        *                      1. ABEND04E RC00C90101 DSNICUMW         *
        *                         ERQUAL5003                           *
        *                      2. ABEND04E RC00C90101 DSNKINSL         *
        *                         ERQUAL5033                           *
        *                      3. Orphan index entries reported by     *
        *                         CHECK INDEX utility                  *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        If the target table of MASS DELETE (DELETE without WHERE clause)
        is a parent table, DB2 needs to do a slow delete. That is to
        delete all records in the table row by row and then de-allocate
        segments except for the first one.

        There was a timing window where concurrent UR could insert some
        records before data segment de-allocation. As a consequence,
        index entries of those inserted records could become orphans,
        and aforementioned problems happened.
        DB2 code has been modified to make sure MASS DELETE to parent
        table in segmented table space will acquire an exclusive gross
        lock first to eliminate the timing window.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM96981
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNISDLE  PM96981

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM96981   DSNISDLE

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

1     MODULES
       DSNISDLE

      LISTEND
 UI13513 COVER LETTER END


 UI13796 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM99039 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS users who have              *
        *                 applied PM80345/UK93671                      *
        *                                                              *
        ****************************************************************
        * PROBLEM DESCRIPTION: 1.ABEND0C4 ICHRFX04+0556 occurred       *
        *                        during MONITOR2 privilege check when  *
        *                        the access control authorization      *
        *                        exit (DSNX@XAC) is used for           *
        *                        authorization checking, IFCID 361     *
        *                        trace is turned ON and                *
        *                        PM80345/UK93671 is applied.           *
        *                                                              *
        *                      2.ABEND0C4-04 DSNXACKP+0716 occurred    *
        *                        when processing an ALTER BUFFERPOOL   *
        *                        command.                              *
        *                                                              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        1.When the access control authorization exit is used for
          authorization and IFCID 361 trace is turned on, this
          ABEND0C4 in ICHRFX04 occurred during the MONITOR2 privilege
          authorization check. This is because PM80345/UK93671
          introduced a logic change that caused an incorrect storage
          token to be passed to the exit when IFCID 361 is turned on.

          This error may also occur for a MONITOR1 privilege check.

          Additional symptoms:
          This may result in an ICH408I or ABEND0C4 in DSNX@XAC when
          the user has the required monitor privilege.

        2.ABEND0C4-04 IN DSNXACKP +0716 occured when processing an
          ALTER BUFFERPOOL command. This is because an incorrect
          length was used to move the command string from the MSTR
          address space to the DBM1 address space.

        1.The code has been changed to provide the correct storage
          token value to the access control authorization exit for
          processing monitor privileges.

        2.The code has been changed to use the correct length to move
          the command string from the MSTR address space to DBM1
          address space during command processing.

1       Additional Keywords: MSGICH408I

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM99039
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXACKP  PM99039
       DSNXA02   PM99039

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM99039   DSNXACKP DSNXA02

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXACKP
       DSNXA02

      LISTEND
 UI13796 COVER LETTER END


 UI13841 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM97985 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS utility users of UNLOAD   *
        *                 DELIMITED with PM79448 (UK92382) applied.    *
        *                 All DB2 10 for z/OS utility users of UNLOAD  *
        *                 DELIMITED with PM79448 (UK92381) applied.    *
        *                 All DB2 11 for z/OS utility users of UNLOAD  *
        *                 DELIMITED                                    *
        ****************************************************************
        * PROBLEM DESCRIPTION: After applying the PTF for PM79448      *
        *                      (UK92381), UNLOAD DELIMITED of an       *
        *                      EBCDIC table containing DBCS/MBCS       *
        *                      data and using the default delimiters   *
        *                      correctly issues MSGDSNU1141I - INVALID *
        *                      DELIMITER CHARACTER ',' (X'6B') and     *
        *                      ends with RC8                           *
        *                                                              *
        *                      As they are default delimiters, UNLOAD  *
        *                      should allow them to be used            *
        *                      successfully.                           *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        After applying the PTF for PM79448 (UK92381), UNLOAD DELIMITED
        of an EBCDIC table containing DBCS and/or MBCS data and using
        the default delimiters, correctly ends with RC8 after issuing
        DSNU1141I - INVALID DELIMITER CHARACTER ',' (X'6B') for an
        invalid column delimiter.

1       PM79448 corrected a code error so that invalid delimiters, even
        if a default value, would cause the UNLOAD to fail which would
        match what was documented in the Utilities Guide and Reference.
        However, this caused a change of behavior which affected some
        customers for which the UNLOAD was working.

        The same error would be expected if the column delimiter was
        valid but the default character delimiter '"' (x'7F') was used.

        As they are default delimiters, UNLOAD should allow them to be
        used successfully.

        This same outcome would occur in DB2 9 with PM79448 (UK92382)
        applied and in DB2 11.
        The fix for PM79448 has been removed and UNLOAD DELIMITED code
        has been changed to allow the default value for the column
        delimiter (x'6B') and for the character delimiter (X'7F') when
        unloading from an EBCDIC table containing MBCS and/or DBCS
        columns and defaulting to the encoding scheme of the table for
        the output.


        As such, the following document changes will be made to the
        Utility Guide and Reference.

        A. DB2 9 for z/OS

        1. Under the chapter for LOAD, Table 36. Maximum delimiter
           values for different encoding schemes:

          Encoding scheme       Maximum allowable value
          EBCDIC SBCS           None
        | EBCDIC DBCS/MBCS      X'3F' (X'7F', X'4B', X'6B' also allowed)
          ASCII/Unicode SBCS    None
          ASCII/Unicode MBCS    X'7F'

        2. Under the chapter for UNLOAD, Table 125. Maximum delimiter
           values for different encoding schemes:

          Encoding scheme       Maximum allowable value
          EBCDIC SBCS           None
        | EBCDIC DBCS/MBCS      X'3F' (X'7F', X'4B', X'6B' also allowed)
          ASCII/Unicode SBCS    None
          ASCII/Unicode MBCS    X'7F'


        B. DB2 10 for z/OS

        1. Under the chapter for LOAD, Table 37. Maximum delimiter
           values for different encoding schemes:

          Encoding scheme       Maximum allowable value
          EBCDIC SBCS           None
        | EBCDIC DBCS/MBCS      X'3F' (X'7F', X'4B', X'6B' also allowed)
          ASCII/Unicode SBCS    None
          ASCII/Unicode MBCS    X'7F'
1
        2. Under the chapter for UNLOAD, Table 127. Maximum delimiter
           values for different encoding schemes:

          Encoding scheme       Maximum allowable value
          EBCDIC SBCS           None
        | EBCDIC DBCS/MBCS      X'3F' (X'7F', X'4B', X'6B' also allowed)
          ASCII/Unicode SBCS    None
          ASCII/Unicode MBCS    X'7F'


        C. DB2 11 for z/OS

        1. Under the chapter for LOAD, Table 36. Maximum delimiter
           values for different encoding schemes:

          Encoding scheme       Maximum allowable value
          EBCDIC SBCS           None
        | EBCDIC DBCS/MBCS      X'3F' (X'7F', X'4B', X'6B' also allowed)
          ASCII/Unicode SBCS    None
          ASCII/Unicode MBCS    X'7F'

        2. Under the chapter for UNLOAD, Table 125. Maximum delimiter
           values for different encoding schemes:

          Encoding scheme       Maximum allowable value
          EBCDIC SBCS           None
        | EBCDIC DBCS/MBCS      X'3F' (X'7F', X'4B', X'6B' also allowed)
          ASCII/Unicode SBCS    None
          ASCII/Unicode MBCS    X'7F'


    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM97985
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DOCUMENTATION:
        PM97985 introduces the following changes to the DB2 10 for z/OS
        Utility Guide and Reference (SC19-4067).

        1. Under the chapter for LOAD, Table 37. Maximum delimiter
           values for different encoding schemes:

          Encoding scheme       Maximum allowable value
          EBCDIC SBCS           None
        | EBCDIC DBCS/MBCS      X'3F' (X'7F', X'4B', X'6B' also allowed)
          ASCII/Unicode SBCS    None
          ASCII/Unicode MBCS    X'7F'

        2. Under the chapter for UNLOAD, Table 127. Maximum delimiter
           values for different encoding schemes:

          Encoding scheme       Maximum allowable value
          EBCDIC SBCS           None
        | EBCDIC DBCS/MBCS      X'3F' (X'7F', X'4B', X'6B' also allowed)
1         ASCII/Unicode SBCS    None
          ASCII/Unicode MBCS    X'7F'
      ACTION:
        The PTF for APAR PM97985 has modified CSECTs in both the
        DSNUT101 and DSNUTILA load modules, affecting the
        utility batch and DB2 DBM1 address spaces.  After the PTF has
        been applied, it will become active in the utility batch address
        space immediately upon job submission, while it will not take
        effect in the DB2 DBM1 address space until DB2 is stopped and
        started.

        The PTF does not have to be applied to all members in a data
        sharing environment simultaneously, and may be staged across
        each member.  However, until the fix is active in both the
        utility batch and DB2 DBM1 address spaces, the problem the PTF
        addresses will not be resolved.
      ACTION:
        See PM97985 APAR/PTF text for additional information.

        After applying the PTF for PM79448, UNLOAD DELIMITED of an
        EBCDIC table containing DBCS/MBCS data and using the default
        delimiters, ends with RC8 and issues MSGDSNU1141I - INVALID
        DELIMITER CHARACTER ',' (X'6B') for an invalid column delimiter.

        This same error would have occurred if the default value for the
        character delimiter (X'7F') had been specified and if the
        column delimiter had been a valid one.

        In order to allow the specific UNLOAD case to succeed and at the
        same time ensure the LOAD utility can process the unloaded data,
        we are adding x'0E'/x'0F' (shift-out/shift-in) around the
        GRAPHIC and VARGRAPHIC unloaded data for the case where the
        default delimiters are used when defaulting to unloading the
        table space in EBCDIC.  UNLOAD already does this when the UNLOAD
        statement explicitly states EBCDIC and LOAD will load the data
        correctly.

        Code is being added for the case when we default to unloading
        DBCS data (GRAPHIC/VARGRAPHIC) in the format of the table space
        when that table space is defined as EBCDIC.  Without the
        Shift-out/shift-in characters, any operation processing the
        delimited data would not be able to determine the end of a DBCS
        column if the delimiters were contained in the DBCS characters.
        That could lead to possible data integrity problems.  LOAD
        FORMAT DELIMITED already has the code to be able to correctly
        load the graphic data when surrounded by x'0E'/x'0F'.

        In summary, this fix will undo the changes made by PM79448.
        However, it will also change the SYSREC dataset output to ensure
        consistency between implicit and explicit specification of the
        EBCDIC parameter and ensure data integrity is not compromised.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNURILD  PM97985
       DSNUULIA  PM97985
       DSNUULVA  PM97985
1
      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM97985   DSNURILD DSNUULIA DSNUULVA

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNURILD
       DSNUULIA
       DSNUULVA

      LISTEND
 UI13841 COVER LETTER END


 UI14060 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PI07855 -
        ****************************************************************
        * USERS AFFECTED: Users of the DSNTIJEN job in DB2 10 for      *
        *                 z/OS.                                        *
        ****************************************************************
        * PROBLEM DESCRIPTION: The DB2 10 for z/OS ENFM process        *
        *                      abends when an invalid database is      *
        *                      detected. MSGDSNU777I is issued and     *
        *                      the ENFM process abends with ABEND04E   *
        *                      RC00E40600 DSNUECML OFFSET504C          *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        During the DB2 10 for z/OS ENFM process a broken DBD (database
        descriptor) was detected and the ENFM process is terminated
        with an abend.

        A DSNU777I message is issued that indicates the name of the
        broken database:

            DSNU777I  DSNUECML - REORG ENFM STATUS -
                   DETECTED BROKEN DATABASE DURING ENFM - <dbname>

        And the following ABEND is taken which terminates the ENFM
        process:

           ABND=04E-00E40600,LOC=DSNUT101.DSNUECML+504C

        During the ENFM processing of the DBD01 directory table space
        DB2 makes sure processed DBDs appear valid. This is accomplished
        by checking their lengths to ensure the DBD data can be
        properly merged for insert into a LOB table space. Lengths and
        control block eye catchers are used for this DBD validation.

        In the reported case a DBD was encountered that had a VSAM
        catalog name that began with the 3 characters 'DBD' and this
        interfered with the ENFM process DBD validation. It made it
        look like the DBD was broken when it really wasn't.
        DB2 ENFM processing code has been changed to improve the DBD
1       validation process. Random 'DBD' character strings found in the
        contents of a database descriptor will no longer give false
        broken database messages that then fail the ENFM process.

        If a broken database is detected during the ENFM process then
        IBM service should be contacted for assistance.

        Additional keywords: DB2MIGV10/K
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PI07855
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUECML  PI07855

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PI07855   DSNUECML

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUECML

      LISTEND
 UI14060 COVER LETTER END


 UI14250 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PI05744 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS users who have applied      *
        *                 PM93887/UK98555(V10)/UK98556(V11).           *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C4 DSNXA07 occurred during a      *
        *                      GRANT ON a stored procedure when        *
        *                      IFCID 141 trace was turned on and       *
        *                      UK98555 or UK98556 was applied.         *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An ABEND0C4 occurred when DB2 tried to write a IFCID 141 trace
        record for a GRANT ON a stored procedure. This is because
        PM93887/UK98555/UK98556 introduced an update that changed the
        way the SQL text was looked up, and the SQL text was not set
        for certain GRANT statement types. This error may also occur
        for GRANT privileges ON FUNCTION, SCHEMA, TYPE, JAR, SEQUENCE,
        and VARIABLE (V11).

        Additional Keywords:
        IFCID141
        OFFSET2ABE (V10)
        OFFSET2AAA (V11)
        The code was changed so that the SQL text is available for all
1       GRANT statement types.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PI05744
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNHSM3A  PI05744
       DSNXA07   PI05744

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PI05744   DSNHSM3A DSNXA07

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNHSM3A
       DSNXA07

      LISTEND
 UI14250 COVER LETTER END


 UI14357 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PI06758 -
        ****************************************************************
        * USERS AFFECTED: All DB2 V10 and V11 users of packages.       *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C4 in DSNGEPLC + 0E4CX when       *
        *                      loading a package after applying        *
        *                      PE APAR PM96597/UK98589/UK98590.        *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When running a package, incorrectly generated code can cause an
        overlay of a flag. This caused the wrong code path to be
        executed which resulted in the above abend.  The incorrect code
        could also cause the wrong package lock duration to be used.
        The incorrectly generated code has been fixed.

        ADDITIONAL KEYWORDS:SQLOVERLAY DB2OVRLAY/K
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PI06758
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNGEFLC  PI06758

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PI06758   DSNGEFLC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1
      MODULES
       DSNGEFLC

      LISTEND
 UI14357 COVER LETTER END


 UK79840 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM51241 -
        ****************************************************************
        * USERS AFFECTED: All DB2 users of the -DISPLAY DATABASE       *
        *                 command.                                     *
        ****************************************************************
        * PROBLEM DESCRIPTION: The -DISPLAY DATABASE command           *
        *                      displayed INCORROUT STATUS field        *
        *                      values for the final summary line of    *
        *                      partitioned table spaces and indexes.   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The -DISPLAY DATABASE command could display INCORROUT STATUS
        field values for the final summary line of partitioned objects
        because the only valid or relevant STATUS field values for an
        entire partitioned object are:  blank, DBETE or DBETE,RECP.
        The -DISPLAY DATABASE command was changed to only display
        the following possible valid or relevant STATUS field values:
        blank, DBETE or DBETE,RECP.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM51241
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DOCUMENTATION:
        Since the -DISPLAY DATABASE command could have displayed
        INCORROUT STATUS  field values for the final summary line of
        partitioned objects any programs or processes that use that
        field need to understand that the only valid or relevant STATUS
        field values for the entire final summary line of partitioned
        object are: blank, DBETE or DBETE,RECP

        The DSNT397I message was updated to describe the final summary
        line for partitioned objects and their possible valid or
        relevant STATUS field values: blank, DBETE or DBETE,RECP.
      DOCUMENTATION:
        The fix for APAR PM25652, introduces a new special option,
        RRTHashOvrFlwRatio. The Utility Guide and Reference and
        The Application Programming Guide documentation on DSNACCOX
        will have a new description of RRTHashOvrFlwRatio as follows:

        Syntax:

         -|---+---' '--------------+---|-
              +-RRTHashOvrFlwRatio-+
              '- -1 ---------------'
1
        Description:
        RRTHashOvrFlwRatio
        Specifies a criterion for recommending that the REORG utility
        is run on a table space. If the following conditions are true,
        DSNACCOX recommends running REORG:
        - The hash access overflow index is being used for access.
        - The number of hash access overflow index entries divided by
          the total number of rows (expressed as a percentage) is
          greater than RRTHashOvrFlwRatio.

        RRTHashOvrFlwRatio is an input parameter of type CHAR(4). The
        default value is ' 15'. A plus sign (+) preceding or following
        the value, or a plus sign by itself indicates that the DSNACCOX
        stored procedure returns the calculated ratio value in the
        result set. A negative value indicates that the criterion is
        not used.

        The ratio of hash access overflow index entries to the total
        number of rows is returned in column RRTHashOvrFlwRatPCT of the
        result set.


        Figure 4. DSNACCOX formula for recommending a REORG on a table
        space has an additional criteria:
         (((QueryType='REORG' OR QueryType='ALL') AND
           (ObjectType='TS' OR ObjectType='ALL')) AND
          (REORGLASTTIME IS NULL AND LOADRLASTTIME IS NULL) OR
          (NACTIVE IS NULL OR NACTIVE > 5) AND
          ((((REORGINSERTS x 100) / TOTALROWS > RRTInsertsPct) AND
            REORGINSERTS > RRTInsertsAbs) OR
           (((REORGDELETE x 100) /  TOTALROWS > RRTDeletesPct) AND
            REORGDELETE > RRTDeleteAbs) OR
           (REORGCLUSTERSENS > 0 AND
            (REORGUNCLUSTINS x 100) / TOTALROWS > RRTUnclustInsPct) OR
           ((REORGDISORGLOB x 100) / TOTALROWS > RRTDisorgLOBPct) OR
        |  (Object is not using hash organization and ((SPACE x 1024) /
                                                RRTDataSpaceRat)) OR
           ((REORGNEARINDREF+REORGFARINDREF) x 100) / TOTALROWS >
                                                RRTIndRefLimit) OR
           REORGMASSDELETE > RRTMassDelLimit OR
           EXTENTS > ExtentLimit) OR
        | ((QueryType='REORG' OR QueryType='ALL') AND
        |  ObjectType='ALL' * AND
        |  Overflow index hash access is used**, AND
        |  ((overflow index TOTALENTRY x 100) / TOTALROWS >
                                                RRTHashOvrFlwRatio)) OR
          ((QueryType='RESTRICT' OR QueryType='ALL') AND
           (ObjectType='TS' OR ObjectType='ALL') AND
           The table space is in advisory or informational reorg
           pending status)

        |Note:
        |  * ObjectType='ALL' must be specified to use this criteria.
        |    for this criterion to be used. If ObjectType='TS' or
        |    ObjectType='IX' is specified, and '+' is specified for
1       |    RRTHashOvrFlwRatio, an error message is issued. If
        |    ObjectType='TS' or ObjectType='IX' is specified, and
        |    '+' is not specified for RRTHashOvrFlwRatio, this
        |    criterion is not used.
        | ** The overflow index is used when SYSINDEXES.HASH ='Y' AND
        |    SYSINDEXSPACESTATS.REORGINDEXACCESS > 0.


        Add the following table entry to table for the
        "DSNACCOX OUTPUT" section.

        Result set row for second DSNACCOX result set
        ----------------------------------------------------------------
        |Column name        | Data type |Description                   |
        ----------------------------------------------------------------
        |RRTHashOvrFlwRatPCT| Double    |This is an optional column,   |
        |                   |           |and it is being returned when |
        |                   |           |there is a plus (+) sign in   |
        |                   |           |the RRTHashOverFlwRatio.      |
        |                   |           |                              |
        |                   |           |If OBJECTTYPE is ALL and REORG|
        |                   |           |is YES, the ratio of Hash     |
        |                   |           |Access overflow index entries |
        |                   |           |to the total number of rows,  |
        |                   |           |expressed as a percentage.    |
        |                   |           |Otherwise null.               |
        |                   |           |                              |
        |                   |           |If the ratio of Hash Access   |
        |                   |           |overflow index entries to the |
        |                   |           |total number of rows does not |
        |                   |           |exceed the value specified for|
        |                   |           |RRTHashOvrFlwRatio or meet the|
        |                   |           |criteria requirement, this    |
        |                   |           |value is null.                |
        ----------------------------------------------------------------
      ACTION:
         ***Action for PM28652:
        See PM28652 APAR/PTF text for additional information.

        <<<<<<<The following block is a sample bind job for 
DSNACCOR  >>
 
        Post-apply actions after applying the fix for APAR PM28652:
        (a) STOP PROC(SYSPROC.DSNACCOR) to suspend DSNACCOR activity
        (b) Rebind package for DSNACCOR. An example on how to do this is
            BIND PACKAGE(DSNACCOR) MEMBER(DSNACCOR) -
                 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.DSNACCOR) to resume DSNACCOR activity
      ACTION:
        Post-apply actions after applying the fix for APAR PM25652:
        (a) STOP PROC(SYSPROC.DSNACCOX) to suspend DSNACCOX activity
        (b) Rebind package for DSNACCOX. An example on how to do this is
            BIND PACKAGE(DSNACCOX) MEMBER(DSNACCOX) -
                 ACTION(REPLACE) ISOLATION(UR) ENCODING(EBCDIC) -
                 LIBRARY('DSN!!0.SDSNDBRM')
            Change 'DSN!!0' to the prefix of your target library name.
1       (c) START PROC(SYSPROC.DSNACCOX) to resume DSNACCOX activity
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSN@CCOR  PM51241
       DSN@CCOX  PM51241
       DSNACCOR  PM51241
       DSNACCOX  PM51241
       DSNTDMUL  PM51241

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM51241   DSN@CCOR DSN@CCOX DSNACCOR DSNACCOX DSNTDMUL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNACCOR
       DSNACCOX
       DSNTDMUL

      MACROS
       DSN@CCOR
       DSN@CCOX

      LISTEND
 UK79840 COVER LETTER END


 UK81198 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM69372 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS       *
        *                 users of DSNACCOR stored procedure with      *
        *                 a non catalog tablespace named SYSRTSTS.     *
        ****************************************************************
        * PROBLEM DESCRIPTION: DSNT408I SQLCODE = -204, ERROR:         *
        *                      SYSIBM.TABLESPACESTATS IS AN UNDEFINED  *
        *                      NAME during DSNACCOR stored procedure.  *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        DSNACCOR stored procedure failed with MSGDSNT408I SQLCODE204
        ERROR: SYSIBM.TABLESPACESTATS IS AN UNDEFINED NAME when
        checking if Real Time Statistics had been migrated to the
        catalog.  DSNACCOR prepares a SELECT IBMREQD from SYSTABLESPACE
        with name='SYSRTSTS' expecting one row to be returned.  In this
        case, there were two rows that existed.  There were two table
        spaces named SYSRTSTS, a user table space and the catalog
        table space, DSNDB06.SYSRTSTS, which was not the first row
        returned in the select.  An additional condition should be
        included on the SELECT to ensure the correct row is returned.
        DSNACCOR has been modified to SELECT IBMREQD for the catalog
        data base name DSNDB06 and SYSRTSTS.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM69372
    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
       DSN@CCOR  PM69372
       DSNACCOR  PM69372

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM69372   DSN@CCOR DSNACCOR

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNACCOR

      MACROS
       DSN@CCOR

      LISTEND
 UK81198 COVER LETTER END


 UK83237 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM84655 -
        ****************************************************************
        * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
        ****************************************************************
        * PROBLEM DESCRIPTION: Hung server threads (DBATs), suspended  *
        *                      out of DSNLQCTL, even though the        *
        *                      TCP/IP connection with the client was   *
        *                      lost during a commit sequence.          *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        A remote requester system operates as a Two Phase Commit
        coordinator.  If a communication error occurs during a commit
        sequence, the associated DB2 server thread (DBAT) may hang
        indefinitely while potentially holding valuable/critical
        database resources that can affect other applications.
        The DB2 Display Thread Detail command report will reflect the
        presence of the DBAT and its connection with the remote
        coordinator even though TCP/IP Display Connection command
        reports indicate that the connection with the coordinator no
        longer exists.  If the communication error occurs during
        phase 1 commit processing, the Display Thread command report
        will also indicate a DSNV465I message condition.
        The problem occurs because DB2 is notified of the communication
        error but then ignores the condition if the DBAT is actually in
        commit processing since commit processing should not be
        interrupted.  The intent is that the connection outage will be
        noticed once the commit (phase 1 or 2) processing is complete
        and a reply is sent back to the coordinator, but the send
        operation may unexpectedly succeed in which case the DBAT will
        hang.
        A DB2 Cancel Thread command must be used to terminate the hung
1       DBAT.

        DB2 has been changed to essentially remember that it has been
        notified of the communication failure in anticipation that the
        send of the commit reply may actually still succeed.  If the
        send of the reply succeeds, the thread will now terminate as
        a result of the known communication failure condition.
      PM89376 -
        ****************************************************************
        * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
        ****************************************************************
        * PROBLEM DESCRIPTION: Fix completion for APAR PM84655.        *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Fix completion for APAR PM84655.

        Fix completion for APAR PM84655.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM84655,PM89376
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNLILOS  PM84655
       DSNLIRTR  PM84655  PM89376
       DSNLIXIT  PM84655
       DSNLQCTL  PM84655
       DSNLTPCF  PM84655

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM84655   DSNLILOS DSNLIRTR DSNLIXIT DSNLQCTL DSNLTPCF
       PM89376   DSNLIRTR

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNLILOS
       DSNLIRTR
       DSNLIXIT
       DSNLQCTL
       DSNLTPCF

      LISTEND
 UK83237 COVER LETTER END


 UK91351 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM74794 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS       *
        *                 utility users of the DSNACCOX stored         *
        *                 procedure                                    *
        ****************************************************************
1       * PROBLEM DESCRIPTION: Three problems for DSNACCOX REORG       *
        *                      RESTRICT:                               *
        *                                                              *
        *                      1. INDEXSPACE column is blank and       *
        *                      should contain the index space name     *
        *                                                              *
        *                      2. OBJECTSTATUS does not have the       *
        *                      partitioned object space(s) that are    *
        *                      in a restrictive state such as AREOR    *
        *                      status.                                 *
        *                                                              *
        *                      3. Output contains a row for partition  *
        *                      0 that should not be there.             *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        DSNACCOX REORG RESTRICT yields:

        1. A result set with INDEXSPACE being blank when it should be
        filled in.

        2. OBJECTSTATUS does not have the partitioned table/index spaces
        restrictive DBET state such as AREOR listed.

        3. Output erroneously containing a line for partition 0.
        DSNACCOX has been changed to:

        1. Fill in the indexspace name when required and possible.

        2. Fill in OBJECT STATUS with the partitioned table space or
        index space restrictive DBET state.

        3. Not put out a line for partition 0.


        The DB2 9 for z/OS Utility Guide and Reference will be changed
        with the following:

        PM74791 introduces the following changes to the DB2 9 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.
1

        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.



        The DB2 10 for z/OS Utility Guide and Reference will be changed
        with the following:


        PM74791 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.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM74794
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DOCUMENTATION:
        PM74794 introduces the following changes to the DB2 10 for z/OS
        Utility Guide and Reference -

        Appendix B. DB2-supplied stored procedures for utility
        operations

        Section - DSNACCOX stored procedure

        Chapter - DSNACCOX output

        Table 145 - Result set row for second DSNACCOX result set
1
        | 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 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.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSN@CCOX  PM74794
       DSNACCOX  PM74794

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM74794   DSN@CCOX DSNACCOX

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNACCOX

      MACROS
       DSN@CCOX

      LISTEND
 UK91351 COVER LETTER END


 UK91533 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM78077 -
        ****************************************************************
        * USERS AFFECTED: All DB2 users of the -DISPLAY DATABASE       *
1       *                 command with the USE or LPL keywords         *
        ****************************************************************
        * PROBLEM DESCRIPTION: The -DISPLAY DATABASE command invoked   *
        *                      with the USE or LPL keyword could       *
        *                      generate extraneous or redundant        *
        *                      lines for partitioned objects           *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The -DISPLAY DATABASE command invoked with the USE or LPL
        keywords could generate extraneous or redundant lines for
        partitioned objects.
        Changed the -DISPLAY DATABASE command with the USE or LPL
        keywords to eliminate extraneous or redundant partition
        information.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM78077
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNTDMUL  PM78077

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM78077   DSNTDMUL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNTDMUL

      LISTEND
 UK91533 COVER LETTER END


 UK91974 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM77090 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS       *
        *                 users of the DB2 scheduler for               *
        *                 administrative tasks                         *
        ****************************************************************
        * PROBLEM DESCRIPTION: Message DSNA679I is not written to the  *
        *                      console as a multi-line message. This   *
        *                      message is split and written as 2       *
        *                      single-line messages instead:           *
        *                                                              *
        *                       N ... DSNA679I  DSNA6BUF THE ADMIN     *
        *                             SCHEDULER DSNADMT CANNOT ACCESS  *
        *                             TASK LIST                        *
        *                       S ... SYSIBM.ADMIN_TASKS, REASON=      *
        *                       N ... SQLCODE -xxx, SQLSTATE yyyyy,    *
        *                             SYSIBM.ADMIN_TASKS               *
        *                                                              *
1       *                      where                                   *
        *                      o the first part of DSNA679I is         *
        *                        a single-line message (log record     *
        *                        type 'N') followed by a continuation  *
        *                        line (log record type 'S')            *
        *                      o the second part of DSNA679I, which    *
        *                        contains the value of the REASON      *
        *                        token, is another single-line         *
        *                        message (log record type 'N')         *
        *                        which could also be followed by       *
        *                        a continuation line (log record       *
        *                        type 'S') if the value of the         *
        *                        REASON token is long and it           *
        *                        wraps                                 *
        ****************************************************************
        * RECOMMENDATION: APPLY PTF                                    *
        ****************************************************************
        The scheduler splits message DSNA679I into 2 parts, and invokes
        WTO to write each part as a single-line message.
        The scheduler is modified to issue DSNA679I as a multi-line
        message as follows:

          M ... DSNA679I  DSNA6BUF THE ADMIN SCHEDULER DSNADMT
          D ... CANNOT ACCESS TASK LIST SYSIBM.ADMIN_TASKS,
          E ... REASON=SQLCODE -xxx, SQLSTATE yyyyy, SYSIBM.ADMIN_TASKS

        with log record types of 'M' (first line of a multi-line
        message), 'D' (data line of a multi-line message), and 'E'
        (end line of a multi-line message).

        If the REASON= line is longer than 71 characters, it is split,
        if possible, at a blank as follows:
          M ... DSNA679I  DSNA6BUF THE ADMIN SCHEDULER DSNADMT
          D ... CANNOT ACCESS TASK LIST SYSIBM.ADMIN_TASKS,
          D ... REASON=SQLCODE -xxx, SQLSTATE yyyyy,
          E ... locn.DSNADM.DSNA6DB2.contoken DSNRRSAF 03

        To make each line of DSNA679I clearer, DSNA679I is subdivided
        differently from how it was subdivided as two single-line
        messages. Therefore, any application that parses DSNA679I
        based on how this message was subdivided and displayed on the
        console must be modified.

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM77090
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        This PTF writes the message DSNA679I to the console as a
        multi-line message, instead of two single-line messages.

        Before this PTF, DSNA679I is split into two parts, each part
        written as a single-line message. For example:

          N ... DSNA679I  DSNA6BUF THE ADMIN SCHEDULER DSNADMT CANNOT
1               ACCESS TASK LIST
          S ... SYSIBM.ADMIN_TASKS, REASON=
          N ... SQLCODE -xxx, SQLSTATE yyyyy, SYSIBM.ADMIN_TASKS

        where:
          o the first part of the message ends at REASON=, and is
            displayed with log record types 'N' (single-line message)
            and 'S' (continuation of a previous line)
          o the second part of the message contains the text
            that follows REASON=, and is displayed with log record
            type 'N' and if necessary, another record with log record
            type 'S' (continuation of a previous line)

        With this PTF, DSNA679I is written to the console as a multi-
        line message. For example:

          M ... DSNA679I  DSNA6BUF THE ADMIN SCHEDULER DSNADMT
          D ... CANNOT ACCESS TASK LIST SYSIBM.ADMIN_TASKS,
          E ... REASON=SQLCODE -xxx, SQLSTATE yyyyy, SYSIBM.ADMIN_TASKS

        where:
          o the first line ends with the name of the scheduler, and
            is displayed with log record type 'M' (first line of a
            multi-line message)
          o the second line ends with the name of the scheduler task
            list and is displayed with log record type 'D' (data line
            of a multi-line message)
          o the third line starts with REASON=, and is displayed with
            log record type 'D' or 'E' (end line of a multi-line
            message), depending on whether the text that follows
            REASON= will wrap
          o the last line is displayed with log record type 'E'

        As a multi-line message, DSNA679I is subdivided differently
        from how it was subdivided as two single-line messages.
        Therefore, any application that parses DSNA679I based on how
        this message was subdivided and displayed on the console must
        be modified. In addition, when this PTF is applied on a member
        by member basis to a DB2 data sharing group, all applications
        that parse DSNA679I for the schedulers of other members must
        be modified to check the log record type of DSNA679I first
        before parsing:
          o If log record type='N', parse DSNA679I as two single-line
            messages.
          o If log record type='M', parse DSNA679I as a multi-line
            message.

        The following post-apply actions are required of all current
        DB2 10 for z/OS customers to activate the changes in this PTF:
        (1) Stop the DB2 scheduler for administrative tasks.
        (2) Start the DB2 scheduler for administrative tasks.

        Each of these actions is detailed below.
        (1) If the DB2 scheduler is running, stop it first by executing
            the following console command:
            MODIFY DSNADMT,APPL=SHUTDOWN
1           where DSNADMT is the name of the scheduler.
        (2) To start the DB2 scheduler again, execute the following
            console command:
            START DSNADMT
            where DSNADMT is the name of the scheduler.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNA6BUF  PM77090
       DSNA6ITK  PM77090

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM77090   DSNA6BUF DSNA6ITK

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNA6BUF
       DSNA6ITK

      LISTEND
 UK91974 COVER LETTER END


 UK92534 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM82709 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 and 10 users of INSTEAD OF         *
        *                 triggers.                                    *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00E20016 due to a storage    *
        *                      leak of blocks allocated by             *
        *                      DSNXETCH UK73809+273.                   *
        *                                                              *
        *                      The eye catcher of the block is TLST.   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        During the processing of an INSTEAD OF TRIGGER, certain
        conditions may cause DB2 to continue processing without freeing
        the TLST control block.
        DB2 code has been corrected to free the storage for TLST control
        blocks in the cases noted above for INSTEAD OF TRIGGER
        processing.

        Additional Keywords: SQLSTORAGE DB2STGLK/K
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM82709
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXETCH  PM82709

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1      PM82709   DSNXETCH

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXETCH

      LISTEND
 UK92534 COVER LETTER END


 UK92537 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM80178 -
        ****************************************************************
        * USERS AFFECTED: All HIR2220 (IRLM220) and HIR2230 (IRLM230)  *
        *                 users.                                       *
        ****************************************************************
        * PROBLEM DESCRIPTION: 1.                                      *
        *                      IRLM ABENDU2019 with MSGDXR116E CODE=09 *
        *                      followed by DB2 ABEND04E-00E30081 in    *
        *                      DSNTLIDE for restart failure.           *
        *                      2.                                      *
        *                      ABEND0C4 in DXRRL1D0 may occur after    *
        *                      DB2/IMS failure in the Notify Exit.     *
        ****************************************************************
        * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
        ****************************************************************
        1. IRLM startup with DB2 auto-start may fail if DB2 restart is
         attempted within 30 seconds or less after DB2 was stopped. IRLM
         issues MSGDXR116E for initialization failure with ABENDU2019
         because the earlier instance of that IRLM was still active.
         The earlier instance of IRLM may wait up to 30 seconds for its
         DBMS Exit Call counter to be cleared, before returning to
         RTM from its ESTAE routine.  This delay may occur if DBMS Exit
         goes through abnormal termination and IRLM FRR code fails to
         decrement its scheduled SRB count. IRLM Estae waits 30 seconds
         before giving up and terminating.
        2. IRLM may also ABEND0C4 in DXRRL1D0 after a failure in DB2 or
         IMS Notify Exit. IRLM FRR in DXRRL1D0 may be in wrong PSW KEY
         when attempting to release IRLM storage (NPL) for the Notify.
        GEN:
        KEYWORDS:

        *** END IMS KEYWORDS ***
        1.
        This APAR will correctly handle the recovery code in IRLM FRR in
        DXRRL1D0. IRLM will decrement the scheduled SRB count (RLMCTSRB)
        so that ECB for quiesce is posted timely and IRLM ESATE doesn't
        have to wait for 30 seconds. In case of handling an error from
        DBMS Status Exit, IRLM will correctly update its counter
        (RLMCTST) so the termination ECB is posted timely.
        2.
        Notify Exit FRR routine in DXRRL1D0 will set the correct PSW KEY
        to avoid ABEND0C4 before returning to RTM.
    COMPONENT:  5695-16401-HIR2230
1   APARS FIXED: PM80178
    SPECIAL CONDITIONS:
      COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DXRRL1D0  PM80178

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM80178   DXRRL1D0

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DXRRL1D0

      LISTEND
 UK92537 COVER LETTER END


 UK92588 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM80149 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 FOR z/OS users who use RECOVER    *
        *                 with the BACKOUT keyword or FlashCopy with   *
        *                 consistency.                                 *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C90101 ERQUAL5013          *
        *                      DSNIBHUN:5013 during RECOVER with       *
        *                      the BACKOUT YES option or FlashCopy     *
        *                      with the CONSISTENT keyword during      *
        *                      the COPY or LOAD utility.               *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        During backout processing during the LOGUNDO phase for RECOVER
        BACKOUT or FlashCopy with consistency DSNIBHUN can abend because
        some log records were not processed.
        DB2 was changed to process all of the required log records.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM80149
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNJRM01  PM80149
       DSNJRM02  PM80149
       DSNJRM03  PM80149
       DSNJR006  PM80149
       DSNUCALU  PM80149

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM80149   DSNJRM01 DSNJRM02 DSNJRM03 DSNJR006 DSNUCALU

1     THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNJRM01
       DSNJRM02
       DSNJRM03
       DSNJR006
       DSNUCALU

      LISTEND
 UK92588 COVER LETTER END


 UK92609 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM71744 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users.                   *
        ****************************************************************
        * PROBLEM DESCRIPTION: DB2 10 for z/OS offers no generic       *
        *                      solution to trigger the externalization *
        *                      of pending real-time statistics into    *
        *                      the catalog tables                      *
        *                      SYSIBM.SYSTABLESPACESTATS and           *
        *                      SYSIBM.SYSINDEXSPACESTATS on demand.    *
        ****************************************************************
        * RECOMMENDATION: APPLY PTF.                                   *
        ****************************************************************
        For applications that rely on real-time statistics (RTS)
        the asynchronous externalization process of RTS might be too
        imprecise. For these kind of applications a callable interface
        that can trigger the externalization of pending RTS changes
        is needed.
        This APAR adds a new MODE option to the ACCESS DATABASE
        command. The new option "STATS" can be used to externalize
        pending real-time statistics.

        New Syntax:

                               .-,-------------.
                               V               |
        
>>-ACCESS--DATABASE(-+---database-name-+-----+-)--------------->
 
                             +-*---------------------+
                             +-dbname1:dbname2-------+
                             +-dbname*---------------+
                             +-*dbname---------------+
                             +-*dbname*--------------+
                             '-*dbstring1*dbstring2*-'


                          .-,----------.
                          V            |
        >--SPACENAM--(--+---space-name-+--------------+--)------------->
                        +-*---------------------------+
                        +-spacename1:spacename2-------+
                        +-spacename*------------------+
1                       +-*spacename------------------+
                        +-*spacename*-----------------+
                        '-*spacestring1*spacestring2*-'

        >--+---------------------------------------+------------------->
           |          .-,---------------------.    |
           |          V                       |    |
           '-PART--(----+-integer-----------+-+--)-'
                        '-integer1:integer2-'

        
>--MODE--(--+-OPEN----+--)------------------------------------><
 
                    +-NGBPDEP-+
                    '-STATS---'


        New option description:

        MODE( mode-value )

          STATS:
          Externalizes the in-memory real-time statistics to the
          appropriate catalog tables. In data sharing environments,
          the in-memory statistics are externalized for all members.
          This mode does not physically open the page sets or change
          the states of the page sets.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM71744
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DOCUMENTATION:
        PM71744 introduces the following changes to externals:

        A new MODE "STATS" is added to the ACCESS DATABASE command.

                               .-,-------------.
                               V               |
        
>>-ACCESS--DATABASE(-+---database-name-+-----+-)--------------->
 
                             +-*---------------------+
                             +-dbname1:dbname2-------+
                             +-dbname*---------------+
                             +-*dbname---------------+
                             +-*dbname*--------------+
                             '-*dbstring1*dbstring2*-'


                          .-,----------.
                          V            |
        >--SPACENAM--(--+---space-name-+--------------+--)------------->
                        +-*---------------------------+
                        +-spacename1:spacename2-------+
                        +-spacename*------------------+
                        +-*spacename------------------+
                        +-*spacename*-----------------+
                        '-*spacestring1*spacestring2*-'

1       >--+---------------------------------------+------------------->
           |          .-,---------------------.    |
           |          V                       |    |
           '-PART--(----+-integer-----------+-+--)-'
                        '-integer1:integer2-'

        
>--MODE--(--+-OPEN----+--)------------------------------------><
 
                    +-NGBPDEP-+
                    '-STATS---'


        New option description:

        MODE( mode-value )

          STATS:
          Externalizes the in-memory real-time statistics to the
          appropriate catalog tables. In data sharing environments,
          the in-memory statistics are externalized for all members.
          This mode does not physically open the page sets or change
          the states of the page sets.


        Information about this new command option will be included in
        the Information Management Software for z/OS Solutions
        Information Center
        (http://pic.dhe.ibm.com/infocenter/dzichelp/v2r2/index.jsp)
        at a later date.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNILSTS  PM71744
       DSNTDDIS  PM71744
       DSNTDSTP  PM71744
       DSN9SCNA  PM71744

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM71744   DSNILSTS DSNTDDIS DSNTDSTP DSN9SCNA

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNILSTS
       DSNTDDIS
       DSNTDSTP
       DSN9SCNA

      LISTEND
 UK92609 COVER LETTER END


 UK92645 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM81200 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users *
        *                 of scalar full select with parallelism.      *
1       ****************************************************************
        * PROBLEM DESCRIPTION: An ABEND04E RC00C90101 can occur at     *
        *                      location DSNIBNRF 5007 ERQUAL5007 when  *
        *                      running a query with parallelism whose  *
        *                      selection list contains a scalar full   *
        *                      select item that participates in an     *
        *                      arithmetic calculation.                 *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An ABEND04E RC00C90101 can occur at DSNIBNRF:5007 ERQUAL5007
        when running a query with parallelism whose selection list
        contains a scalar full select that participates in an arithmetic
        calculation.

        The failure occurs because the data type and length of the
        scalar full select item is misinterpreted by DB2 during the
        parallelism process.

        The following is an example of such failing query.

          SELECT X1, CAST(C2 AS VARCHAR(10)), CAST(C3 AS VARCHAR(5))
          FROM (SELECT X1, (SELECT DECFLOAT16_1
                            FROM TB1
                            WHERE X1 = T.X2+10) + 10000 AS C2,
                            DECFLOAT16_1 C3
                            FROM T ) T1
          WHERE X1 = '9'
          AND   C2 = 10019.999
          AND   C3 = 9.999 ;

        DB2 is modified to interpret the data type and length of a
        scalar full select item (in the selection list of a query)
        properly during parallelism.

        Additional Keywords: PARALLELISM SQLPARALLELISM
                             SQLSCALAR SQLFULLSELECT SQLSCALARFULSEL
                             DB2PARALL/K

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM81200
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      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
1       rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOGRL  PM81200

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM81200   DSNXOGRL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOGRL

      LISTEND
 UK92645 COVER LETTER END


 UK92649 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM83982 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 for zOS.                    *
        ****************************************************************
        * PROBLEM DESCRIPTION: DB2 thread TCB abended with ABEND04F    *
        *                      during DB2 abnormal termination after   *
        *                      an abend RETRY with FRBRC2 RC00F30805.  *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        During DB2 abnormal termination, an IMS TCB had abended and
        a RETRY was done by the recovery routine in DSNAPRHX.  An
        FRBRC2 RC00F30805 was returned to the attach indicating
        that DB2 was terminating, but DSNAPRHX did not set a tracking
        flag correctly.  This allowed a CALLRTM ABTERM with ABEND04F
        to be issued on the IMS TCB after the TCB was out of DB2.
        The DSNAPRHX recovery routine has been changed to set the
        tracking flag correctly when DB2 is in abnormal termination.
    COMPONENT:  5740-XYR01-HIZAA10
    APARS FIXED: PM83982
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR01 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        ***Action for PM83982:

        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
1       -START DB2,PARM=...

        These commands are not necessary if you re-IPL after applying
        the PTF.
      ACTION:
        In order for this PTF to be fully effective, an IPL with CLPA or
        REFRESH DB2,EARLY is required.  The DB2 member should be
        stopped before issuing the REFRESH DB2, EARLY command.
      ACTION:
        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 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 PM57744:

        This PTF requires either an EARLY code refresh or a re-IPL of
        zOS.

        To refresh, enter the following commands after applying
        the PTF:

        MODIFY LLA,REFRESH
        -STOP DB2 ... (only if the DB2 subsystem is started)
        -REFRESH DB2,EARLY
        -START DB2,PARM=...

        These commands are not necessary if you re-IPL after applying
        the PTF.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNAPRHX  PM83982

1     CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM83982   DSNAPRHX

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNAPRHX

      LISTEND
 UK92649 COVER LETTER END


 UK92651 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM83847 -
        ****************************************************************
        * USERS AFFECTED: All users of the -START DB2 command in DB2   *
        *                 9.1 for z/OS and DB2 10 for z/OS are         *
        *                 affected by this change.                     *
        ****************************************************************
        * PROBLEM DESCRIPTION: During DB2 start up, one or both of     *
        *                      the following errors occurs:            *
        *                      (1) DB2 start up fails with ABEND0C4    *
        *                          reason code 4 at DSNZLNAM           *
        *                          UK61350+106 in module DSNZINIT      *
        *                      (2) One or more data set names          *
        *                          displayed in messages DSNZ016I and  *
        *                          DSNZ017I are blank or corrupted.    *
        *                      The errors occur only when DB2 loads    *
        *                      one or more of the following modules:   *
        *                       - the zparm module                     *
        *                       - the DSNHDECP module                  *
        *                       - a DB2 authorization exit module      *
        *                       - a DB2 date and time exit module      *
        *                      from the 129th or subsequent data set   *
        *                      in the system link list concatenation.  *
        ****************************************************************
        * RECOMMENDATION: Apply the fixing PTF for this APAR.          *
        ****************************************************************
        During start up, DB2 writes console message DSNZ016I to report
        the name(s) of the data set(s) from which it loaded the zparm,
        DSNHDECP, and authorization exit modules.

        DB2 10 also writes console message DSNZ017I to report the
        the name(s) of the data set(s) from which it loaded the date
        and time exit modules.

        Currently, if one or more of those modules is loaded from the
        129th or subsequent data set in the system link list
        concatenation, one or both of the following errors can occur
        during DB2 start up:

        - One or more data set names displayed in messages DSNZ016I
          and DSNZ067I can be blank or corrupted
        - DB2 start up can fail with ABEND0C4 reason 4 at DSNZLNAM
          UK61350+106 in module DSNZINIT.
1
        In response, this APAR fixes DB2 so that it can determine data
        set names for the maximum of 256 data sets in the system link
        list concatenation.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM83847
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNZLNAM  PM83847

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM83847   DSNZLNAM

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNZLNAM

      LISTEND
 UK92651 COVER LETTER END


 UK92704 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM67669 -
        ****************************************************************
        * USERS AFFECTED: Internal serviceability: diagnostic logging  *
        ****************************************************************
        * PROBLEM DESCRIPTION: Internal serviceability: diagnostic     *
        *                      logging                                 *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Internal serviceability: diagnostic logging
        Internal serviceability: diagnostic logging
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM67669
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNB5COM  PM67669
       DSNKFRMT  PM67669

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM67669   DSNB5COM DSNKFRMT

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNB5COM
       DSNKFRMT
1
      LISTEND
 UK92704 COVER LETTER END


 UK92705 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM83680 -
        ****************************************************************
        * USERS AFFECTED: Users of the DB2 for z/OS Version 10         *
        *                 precompiler or coprocessor using the         *
        *                 SQL(ALL) SQL processing option.              *
        ****************************************************************
        * PROBLEM DESCRIPTION: Executing the precompiler or            *
        *                      coprocessor with SQL(ALL)               *
        *                      may result in ABEND0C4 RC11 in DSNHSM3. *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Executing the DB2 precompiler or coprocessor
        with the SQL(ALL) option may
        result in the reported abend when processing an SQL statement
        containing an indentifier that begins with a letter near the
        end of the alphabet.

        An SQL statement like the following may result in the abend
        because of the identifier WS-FIELD:

        EXEC SQL
            SELECT COL1 INTO :HV1 FROM T1
            WHERE COL2 = :WS-FIELD
        END-EXEC.

        The abend only occurs when the SQL(ALL) option is used.
        It does not occur when the SQL(DB2) option is specified.

        Optional keywords:
          DB2PRECOMPILER  DB2COPROCESSOR
        The DB2 precompiler and coprocessor logic is modified so that
        the reported abend no longer occurs.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM83680
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNHSM3   PM83680

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM83680   DSNHSM3

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNHSM3
1
      LISTEND
 UK92705 COVER LETTER END


 UK92791 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM82151 -
        ****************************************************************
        * USERS AFFECTED: All DB2 IMS Attachment users.                *
        ****************************************************************
        * PROBLEM DESCRIPTION: IMS Attachment Prepare to Commit will   *
        *                      issue a new return code to support      *
        *                      IMS APARs V11 PM69915, V12 PM70167 and  *
        *                      V13 PM79247.                            *
        *                      The general problem occurs when an IMS  *
        *                      transaction issues a commit on a        *
        *                      DB2 distributed connection and the      *
        *                      DB2 Attachment Prepare to Commit code   *
        *                      returns with a vote no.  The underlying *
        *                      cause of the commit failure on the      *
        *                      remote connection was a RACF failure    *
        *                      at the remote DB2.                      *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        IMS Attachment Prepare to Commit will issue a new return code to
        support IMS APARs V11 PM69915, V12 PM70167 and V13 PM79247.
        The general problem occurs when an IMS transaction issues a
        commit on a DB2 distributed connection and the
        DB2 Attachment Prepare to Commit code returns with a vote no.
        The Prepare to Commit code will be changed to issue RC16 for
        distributed commit failures.
        Module DSNMDR00 Prepare to Commit has been changed to
        issue RC16 for distributed commit failures.
    COMPONENT:  5740-IY100-HIYAA10
    APARS FIXED: PM82151
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-IY100 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        This APAR provides changes to support IMS APARs PM69915 (V11),
        PM70167 (V12) or PM79247 (V13).
        The fix for this APAR PM82151 should be installed to obtain
        the full benefit of the changes provided in these IMS APARs.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNMDR00  PM82151

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM82151   DSNMDR00

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNMDR00
1
      LISTEND
 UK92791 COVER LETTER END


 UK92801 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM82268 -
        ****************************************************************
        * USERS AFFECTED: DB2 users.                                   *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C4 in DSNB1RLS or DSNB1DCM.       *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Abends are due to a residual PBA0 control block being left on
        the read-lsn chain for a scrollable cursor.  If the read-lsn is
        registered with no read claim held - or if it is registered for
        a partition when the agent holds a tablespace-level drain - the
        block will not be found at commit time and removed from the
        chain.  Once the block has been freed and reused, its presense
        on the read-lsn chain can result in an ABEND0C4 in DSNB1DCM or
        DSNB1RLS.
        The read-lsn registration code has been modified to ensure
        that the PBA0 block is correctly chained.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM82268
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNB1RLS  PM82268

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM82268   DSNB1RLS

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNB1RLS

      LISTEND
 UK92801 COVER LETTER END


 UK92833 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM83176 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9, DB2 10 for z/OS users of Native   *
        *                 SQL procedure and non-inline SQL scalar      *
        *                 function.                                    *
        ****************************************************************
        * PROBLEM DESCRIPTION: Unexpected SQLCODE -199 could be        *
        *                      issued when rebind, incremental rebind  *
1       *                      or deployment of a Native SQL procedure *
        *                      or a non-inline SQL scalar function     *
        *                      which contains an SQL statement that    *
        *                      references a single SQL variable in     *
        *                      select list and there are parentheses   *
        *                      around it.                              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Unexpected SQLCODE -199 could be issued when rebind,
        incremental rebind or deployment of a Native SQL procedure
        or a non-inline SQL scalar function which contains an
        SQL statement that references a single SQL variable in
        select list and there are parentheses around it.

        The following example could recreate the unexpected sqlcode.

        CREATE PROCEDURE MYPROC( )
        LANGUAGE SQL
        L1:BEGIN
          DECLARE VAR1  INTEGER;
          DECLARE VAR2  INTEGER;
          SELECT (VAR1) INTO VAR2 FROM T1;
        END

        SQLCODE -199 is issued when rebind, incremental rebind or
        deployment the above native SQL procedure.
        DB2 is updated to handle the SQL statement in native SQL
        procedure or non-inline SQL scalar function which contains
        SQL variable with parentheses around it correctly.
        Additional Keywords: SQLNATIVESQLPL SQLCODE199 SQLREBIND
                             SQLINCREBIND SQLDEPLOY
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM83176
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        ***Action for PM83176
        TYPE:  ACT

        PM83176 corrects a problem of sqlcode -199 issued during rebind
        when a native SQL procedure or a non-inline SQL scalar function
        contains an SQL statement with a single SQL valiable in the
        select list with parentheses around it.

        After the application of this PTF, ALTER PROCEDURE REGENERATE is
        required for each native SQL procedure that is affected, or
        ALTER FUNCTION REGENERATE is required for each non-inline SQL
        scalar function that is affected. Review the PTF cover
        letter to determine which, if any, native SQL procedure
        could be affected by this change.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNHSM1   PM83176
       DSNHSM2P  PM83176
1      DSNXOYNS  PM83176
       DSNXOYSR  PM83176

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM83176   DSNHSM1  DSNHSM2P DSNXOYNS DSNXOYSR

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNHSM1
       DSNHSM2P
       DSNXOYNS
       DSNXOYSR

      LISTEND
 UK92833 COVER LETTER END


 UK92837 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM82351 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 10 for z/OS who use IBM     *
        *                 OmniFind Text Search.                        *
        ****************************************************************
        * PROBLEM DESCRIPTION: A performance degradation may occur     *
        *                      when omnifind text search is used.      *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        A performance degradation may occur when omnifind text search
        is used in a query.

        When omnifind functions are used in a predicate, in some cases
        rowid index can be used but it is not, which can cause a
        performance problem.

        DB2 code has been modified to address the problem mentioned.

        Additional keywords: TEXTSEARCH SQLPERFORMANCE

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM82351
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM82351:

        See PM82351 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM82351 corrects a problem where rowid index may not be used
        to evaluate omnifind function in a predicate when it should.
        It may cause performance problem for queries with omnifind
        function in a predicate.
1
        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOOFP  PM82351
       DSNXOSCF  PM82351

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM82351   DSNXOOFP DSNXOSCF

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOOFP
       DSNXOSCF

      LISTEND
 UK92837 COVER LETTER END


 UK92838 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM78196 -
        ****************************************************************
        * USERS AFFECTED: All users of the DSNTIJTC job.               *
        ****************************************************************
        * PROBLEM DESCRIPTION: Users reported that some columns in     *
        *                      the catalog are not updatable but it    *
        *                      is documented otherwise.                *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When running the DSNTIJTC job to migrate to DB2 10 for z/OS,
        the CATMAINT utility changes some catalog columns to become
        updatable. However, users reported that some columns are not
        updatable which is inconsistent to the documentation.

        This APAR/PTF provides serviceability enchancement so that
        CATMAINT utility will put out additional DSNU777I messages
        to indicate that the columns are changed to become updatable.
        In addition, DB2 code has been updated so that CATMAINT
        will take an abend if it fails to make the change.

        The additional DSNU777I messages will look like this:

        DSNU777I  @ 065 17:09:04.95 DSNUECM6 - CATMAINT UPDATE STATUS -
          SYSCOLUMNS.UPDATES HAS BEEN SET TO 'Y' FOR 
<table>.<column>
 
        DB2 code has been updated to provide serviceability enchancement
        in the CATMAINT utility.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM78196
    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
       DSNUECM6  PM78196

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM78196   DSNUECM6

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUECM6

      LISTEND
 UK92838 COVER LETTER END


 UK92843 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM80284 -
        ****************************************************************
        * USERS AFFECTED: DB2 users of wlm-managed user-defined        *
        *                 functions (UDFs) and/or stored procedures    *
        *                 (SPs) that specify minimum number of WLM     *
        *                 stored procedure address spaces on a WLM     *
        *                 stored procedure environment by setting      *
        *                 MNSPAS parameter on the WLM start up JCL.    *
        ****************************************************************
        * PROBLEM DESCRIPTION: When a WLM stored procedure             *
        *                      environment is set to have a minimum    *
        *                      number of address spaces with the       *
        *                      MNSPAS paramater set in the startup     *
        *                      JCL then the MNSPAS parameter is        *
        *                      removed to set to 0 with the intention  *
        *                      of not having a minimum number of       *
        *                      address spaces and the WLM environment  *
        *                      is refreshed, unexpectedly high number  *
        *                      of address spaces are started.          *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When the WLM environment is refreshed, the parameter to control
        the minimum number of service tasks in the environment is not
        reset. This may cause WLM to start many address spaces to
        maintain the minimum number of service tasks.
        Internal variable that sets minimum number WLM service tasks
        is initialiazed on refresh of WLM stored procedure environment.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM80284
    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  PM80284

1     CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM80284   DSNX9WLM

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNX9WLM

      LISTEND
 UK92843 COVER LETTER END


 UK92851 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM80291 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS       *
        *                 utility users of the DSNUTILU or DSNUTILS    *
        *                 utility stored procedure                     *
        ****************************************************************
        * PROBLEM DESCRIPTION: Data sets that are dynamically          *
        *                      allocated by utilities being executed   *
        *                      from either the DSNUTILU or DSNUTILS    *
        *                      stored procedure are not being          *
        *                      deallocated when the utility abnormally *
        *                      terminates.                             *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        The UNLOAD utility was invoked from a utility stored procedure
        and abnormally terminated because the dynamically allocated
        output data set (SYSREC) was too small.  The recovery routine
        failed to deallocate the SYSREC data set resulting in the WLM
        address space needing to be either refreshed or cancelled
        to deallocate it.
        The utility recovery routine is fixed to dynamically deallocate
        any files that were dynamically allocated by the utility when
        the utility is called by a stored procedure.

        However, with this change, the utility needs to ensure that it
        is the only task running in the WLM-managed address space.

        DB2 for z/OS documents this requirement as NUMTCB=1 when
        running in a WLM-managed address space.

        PM80291 introduces the following new message when the utility
        detects that the WLM managed address space had been started
        with NUMTCB<>1:

        DSNU022I
        csect-name -  A UTILITY RUNNING UNDER A STORED PROCEDURE
        REQUIRES A WLM ENVIRONMENT WITH NUMTCB=1. UTILID utility-ID IS
        RUNNING WITH NUMTCB = tcb-number.

        Explanation
        When the utility stored procedure invoked a utility, the stored
1       procedure was running in a stored procedure address space that
        was started with NUMTCB>1. The stored procedure address space in
        which the utility stored procedure runs must be started with
        NUMTCB=1 be started with NUMTCB=1.

        csect-name
        The name of the control section that issued the message.

        utility-ID
        The utility identifier or the UID parameter that was used in the
        job step.

        tcb-number
        The NUMTCB parameter of the job that started the WLM-managed
        stored procedure address space. The NUMTCB value represents the
        maximum number of task control blocks (TCBs) that can run
        concurrently in an address space that is initiated by the WLM
        environment.

        System action
        Execution of the utility is stopped.

        System programmer response
        Change the PROCLIB member that was used to start the WLM-managed
        stored procedure address space to specify NUMTCB=1. Then,
        refresh the WLM environment and run the utility again.

        Severity
        8 (error)

        Information about this new message, DSNU022I, 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.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM80291
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        The fix for PM80291 enforces the documented requirement that
        when the utility is invoked from a stored procedure, NUMTCB=1
        must be specified in the proc that started the WLM managed
        address space where the utility is running.

        PM80291 introduces the following message to the DB2 10 for z/OS
        Messages:

        DSNU022I
        csect-name -  A UTILITY RUNNING UNDER A STORED PROCEDURE
        REQUIRES A WLM ENVIRONMENT WITH NUMTCB=1. UTILID utility-ID IS
        RUNNING WITH NUMTCB = tcb-number.

        Explanation
        When the utility stored procedure invoked a utility, the stored
1       procedure was running in a stored procedure address space that
        was started with NUMTCB>1. The stored procedure address space in
        which the utility stored procedure runs must be started with
        NUMTCB=1.

        csect-name
        The name of the control section that issued the message.

        utility-ID
        The utility identifier or the UID parameter that was used in the
        job step.

        tcb-number
        The NUMTCB parameter of the job that started the WLM-managed
        stored procedure address space. The NUMTCB value represents the
        maximum number of task control blocks (TCBs) that can run
        concurrently in an address space that is initiated by the WLM
        environment.

        System action
        Execution of the utility is stopped.

        System programmer response
        Change the PROCLIB member that was used to start the WLM-managed
        stored procedure address space to specify NUMTCB=1. Then,
        refresh the WLM environment and run the utility again.

        Severity
        8 (error)

        Information about this new message, DSNU022I, will be
        included in the Information Management Software for z/OS
        Solutions Information Center
        (http://publib.boulder.ibm.com/infocenter/imzic) at a later
        date.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSN@TILS  PM80291
       DSN@TILU  PM80291
       DSNUGBAC  PM80291
       DSNUTILS  PM80291
       DSNUTILU  PM80291

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM80291   DSN@TILS DSN@TILU DSNUGBAC DSNUTILS DSNUTILU

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUGBAC
       DSNUTILS
       DSNUTILU

      MACROS
       DSN@TILS
       DSN@TILU
1
      LISTEND
 UK92851 COVER LETTER END


 UK92861 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM81502 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of the   *
        *                 NORMALIZE_STRING built-in function           *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C6 at CUNMUNI.CUN4MDEC + x'892'   *
        *                      when DB2 calls Unicode services for     *
        *                      the NORMALIZE_STRING built-in function. *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        ABEND0C6 at CUNMUNI . CUN4MDEC + x'892' may occur when DB2 for
        z/OS calls Unicode services for the NORMALIZE_STRING built-in
        function.  One of the parameters, CUN4BNPR_DDA_Buf_Ptr,
        that DB2 passes to Unicode services should be allocated on
        a double byte boundary.  If it is not then Unicode services
        may abend with an ABEND0C6.  It is also possible to get an
        ABEND0C1.

        Here is an example :
        -- create the table
        CREATE TABLE T1 (C1 CHAR(5)) CCSID UNICODE;
        INSERT INTO T1 VALUES ('ROW1');

        -- invoke the built-in function which may result in an ABEND
        SELECT NORMALIZE_STRING( C1, NFKD ) FROM  T1;

        DB2 for z/OS has been changed to explicitly allocate the buffer
        for CUN4BNPR_DDA_BUF_PTR on a double byte boundary.

        Additional keywords : SQLNORMALIZESTRING

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM81502
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXRSB2  PM81502
       DSNXRS39  PM81502

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM81502   DSNXRSB2 DSNXRS39

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXRSB2
1      DSNXRS39

      LISTEND
 UK92861 COVER LETTER END


 UK92863 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM83374 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 and 10 for zOS users               *
        *                            that execute static SQLs.         *
        ****************************************************************
        * PROBLEM DESCRIPTION: When a VALUES INTO statement with       *
        *                      a DECFLOAT type host variable is        *
        *                      executed, DB2 can incorrectly issue     *
        *                      an SQLCODE -30020.                      *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When a VALUES INTO statement with a host variable is
        executed, DB2 internally processes the host variable
        information (type, length etc.) using SQLDA structure.
                                                             .
        In the reported case, a DECFLOAT type host variable was
        used for a VALUES INTO statement, but the incorrect length
        value was internally set in the SQLDA for the DECFLOAT type
        host variable. For a remote application, it can cause the
        termination of DB2 connection after SQLCODE -30020.
                                                                   .
        The same problem can occur when executing
        1) A SET host-variable statement with a DECFLOAT type host
           variable.
        2) A static query statement that uses a DECFLOAT type column
           or host variable after the belonging package was bound with
           the subsystem parameter DESCSTAT = NO.
        3) For DB2 10 for zOS, any above statement that uses TIMESTAMP
           WITH TIME ZONE type host variable / column.
        DB2 has been modified to correctly handle DECFLOAT type
        (and TIMESTAMP WITH TIMEZONE type for DB2 10 for zOS)
        host variable or column for the statements described above.
                                                                  .
        Related keyword: SQLCODE30020
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM83374
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXEDC1  PM83374

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM83374   DSNXEDC1

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1
      MODULES
       DSNXEDC1

      LISTEND
 UK92863 COVER LETTER END


 UK92875 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM76266 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of RUNSTATS        *
        *                 utility collecting statistics using          *
        *                 TABLESAMPLE SYSTEM keywords.                 *
        ****************************************************************
        * PROBLEM DESCRIPTION: COLCARD is 0 in catalog table           *
        *                      SYSIBM.SYSCOLSTATS and                  *
        *                      SYSIBM.SYSCOLUMNS after RUNSTATS        *
        *                      TABLESAMPLE SYSTEM with no RTS          *
        *                      available.                              *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        A RUNSTATS TABLESAMPLE SYSTEM was executed on a non empty
        table space, when Real Time Statistics (RTS) was not available.
        The utility reported zero COLCARD values in MSGDSNU625I and
        MSGDSNU615I.
        The catalog tables SYSCOLSTATS and SYSCOLUMNS were updated
        with the incorrect zero values.
        The utility message MSGDSNU3343I was issued to indicate the
        missing RTS information. However no error or warning message
        was issued by the utility. The RUNSTATS utility ended with
        return code 0.
        When RUNSTATS TABLESAMPLE SYSTEM n is specified (where n is
        the rate) and when RTS information is not available
        the code was modified to issue MSGDSNU3346I -
        'REAL-TIME STATISTICS INFORMATION MISSING FOR obj-type
        obj-qual.obj-name. SAMPLING RATE CHANGED TO 100'.
        The utility will set the sampling rate to 100 and continue
        processing. The utility will end with RC=4.
        However if TABLESAMPLE SYSTEM AUTO is specified,
        the sampling rate is set to 100 and MSGDSNU3343I is issued
        with RC=0.

        The PTF for APAR PM76266 has added a new message
        MSGDSNU3346I to the Messages manual.

        DSNU3346I REAL-TIME STATISTICS
        INFORMATION MISSING FOR obj-type
        obj-qual.obj-name.
        SAMPLING RATE CHANGED TO 100.

        Explanation: The utility could not read necessary
        information from real-time statistics tables for the
        object.
1       obj-type: The type of object.
        obj-qual.obj-name: The name of the object,as a qualified name.

        System action: RUNSTATS sets the sampling rate to 100, and
        continues to run.

        System programmer response: If a sampling rate of 100 is
        appropriate, no action is required. Otherwise, run the
        REORG TABLESPACE utility on the specified object to
        re-establish values in the real-time statistics tables.
        Then run RUNSTATS with TABLESAMPLE SYSTEM n again.

        Severity: 4 (warning)

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM76266
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DOCUMENTATION:
        The PTF for APAR PM76266 has added a new message
        MSGDSNU3346I to the Messages manual.

        DSNU3346I REAL-TIME STATISTICS
        INFORMATION MISSING FOR obj-type
        obj-qual.obj-name. SAMPLING RATE CHANGED TO 100.

        Explanation: The utility could not read necessary
        information from real-time statistics tables for the
        object.
        obj-type: The type of object.
        obj-qual.obj-name: The name of the object,as a qualified name.

        System action: RUNSTATS sets the sampling rate to 100, and
        continues to run.

        System programmer response: If a sampling rate of 100 is
        appropriate, no action is required. Otherwise, run the
        REORG TABLESPACE utility on the specified object to
        re-establish values in the real-time statistics tables.
        Then run RUNSTATS with TABLESAMPLE SYSTEM n again.

        Severity: 4 (warning)

        Information about the new message DSNU3346I will be
        included in the Information Management Software for z/OS
        Solutions Information Center
        (http://publib.boulder.ibm.com/infocenter/imzic) at a later
        date.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNFMDIR  PM76266
       DSNFUDRE  PM76266
       DSNUGPDS  PM76266
       DSNUGPST  PM76266
       DSNUMSGE  PM76266
1      DSNUSITS  PM76266

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM76266   DSNFMDIR DSNFUDRE DSNUGPDS DSNUGPST DSNUMSGE DSNUSITS

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNFMDIR
       DSNFUDRE
       DSNUGPDS
       DSNUGPST
       DSNUMSGE
       DSNUSITS

      LISTEND
 UK92875 COVER LETTER END


 UK92878 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM81749 -
        ****************************************************************
        * USERS AFFECTED: All DB2 users in data sharing with           *
        *                 partitioned objects.                         *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C202AA in DSNB1SWD         *
        *                      ABEND04E RC00C202B2 in DSNB1PPP         *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When inquiring about the retained information of a page set
        P-lock on a partitioned object, the wrong result may be
        returned if the specified part number is greater than 255.
        DB2 has been fixed to expand the part number field in the
        retained page set P-lock query interface so that a partition
        number that is larger than 255 is handled correctly.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM81749
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNB1CKP  PM81749
       DSNB1DA2  PM81749
       DSNB1DRA  PM81749
       DSNB1LDA  PM81749
       DSNB1LDN  PM81749
       DSNB1PM2  PM81749
       DSNB1QLK  PM81749
       DSNB1RRL  PM81749
       DSNB1RRS  PM81749
       DSNB5SPC  PM81749

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1      PM81749   DSNB1CKP DSNB1DA2 DSNB1DRA DSNB1LDA DSNB1LDN DSNB1PM2
                 DSNB1QLK DSNB1RRL DSNB1RRS DSNB5SPC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNB1CKP
       DSNB1DA2
       DSNB1DRA
       DSNB1LDA
       DSNB1LDN
       DSNB1PM2
       DSNB1QLK
       DSNB1RRL
       DSNB1RRS
       DSNB5SPC

      LISTEND
 UK92878 COVER LETTER END


 UK92899 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM81926 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS       *
        *                 users.                                       *
        *                 Specifically those where trusted contexts    *
        *                 are defined.                                 *
        ****************************************************************
        * PROBLEM DESCRIPTION: The Display Thread command report       *
        *                      contains an improperly indented         *
        *                      DSNV485I (V485) message.  This also     *
        *                      prevents the SYSPROC.ADMIN_COMMAND_DB2  *
        *                      stored procedure from properly          *
        *                      interpreting the result.                *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When a DB2 for z/OS thread is associated to a trusted context,
        the Display Thread command report will issue a DSNV485I (V485)
        message to identify the characteristics of the trusted context
        but the message is improperly indented.  This affects the
        readability of the Display Thread command report and also
        causes the SYSPROC.ADMIN_COMMAND_DB2 stored procedure to
        misinterpret the result.

        DB2 has been changed to correct the indentation of message
        DSNV485I to align itself with other messages related to the
        thread being reported.  When specific fields of the DSNV485I
        message are long (TRUSTED CONTEXT and ROLE) and must be
        continued to the next line of the report, the values will be
        further indented to assist in the readability of the message
        contents.
        Example:
         &dis thd(*)
1        DSNV401I  & DISPLAY THREAD REPORT FOLLOWS -
         DSNV402I  & ACTIVE THREADS -
         NAME     ST A   REQ ID           AUTHID   PLAN     ASID TOKEN
         TEST0001 RA *     1 CTHDCORID001 ADMF001  DONSQL1  0055    10
          V485-TRUSTED CONTEXT=MYCTX67891123456789212345678931234567...
                 951234567896123456789712345678981234567899123456789...
                 123456789212345678,
               SYSTEM AUTHID=ADMF001,
               ROLE=ROLE56789112345678921234567893123456789412345678...
                 612345678971234567898123456789912345678911234567891...
                 2345678
          V445-USIBMSY.SYEC715A.CAEB27DD6855=10 ACCESSING DATA FOR
           ::FFFF:9.30.112.76
         DISPLAY ACTIVE REPORT COMPLETE
         DSN9022I  & DSNVDT '-DIS THD' NORMAL COMPLETION
        The SYSPROC.ADMIN_COMMAND_DB2 stored procedure will now be able
        to properly interpret the message.
        * Warning: *
        Users should be aware that the format of the Display Thread
        command report, specifically the DSNV485I (V485) message, has
        been changed which may impact automation that interprets the
        result.  Before applying this change, users should identify any
        automation that may be affected and adapt this automation to
        tolerate the new form.
        Data Sharing users should be aware that group members may
        report different forms of the message until this change is
        fully deployed to all members of the group.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM81926
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        ***Action for PM81926:
        Users should be aware that the format of the Display Thread
        command report, specifically the DSNV485I (V485) message, has
        been changed which may impact automation that interprets the
        result.  Before applying this change, users should identify any
        automation that may be affected and adapt this automation to
        tolerate the new form.
        Data Sharing users should be aware that group members may
        report different forms of the message until this change is
        fully deployed to all members of the group.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNFMDIR  PM81926
       DSNFVDIR  PM81926
       DSNLDTI2  PM81926
       DSNVDTA   PM81926
       DSNVDTM   PM81926

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM81926   DSNFMDIR DSNFVDIR DSNLDTI2 DSNVDTA  DSNVDTM

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

1     MODULES
       DSNFMDIR
       DSNFVDIR
       DSNLDTI2
       DSNVDTA
       DSNVDTM

      LISTEND
 UK92899 COVER LETTER END


 UK92913 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM78563 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS Workfile database users  *
        ****************************************************************
        * PROBLEM DESCRIPTION: SQLCODE497 -497 during DDL CREATE       *
        *                      TABLESPACE in Workfile database after a *
        *                      recent -START DATABASE command against  *
        *                      the database (without SPACENAM)         *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        If Workfile database did not have any table spaces, when a
        -START DATABASE command was issued (without SPACENAM), the DBD
        for this database was brought to memory but then mistakenly not
        released.

        As a result, a residual DBD from before was kept, which kept
        some table space object identifiers (OBIDs) unavailable for
        reuse despite the table spaces having been dropped earlier.
        DB2 code has been changed to release a DBD for Workfile
        database at -START DATABASE time if the database contains no
        table spaces.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM78563
    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  PM78563

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM78563   DSNIBWAC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIBWAC

      LISTEND
 UK92913 COVER LETTER END


1UK92979 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM84388 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of parallelism for *
        *                 queries that sort using range partitioning.  *
        ****************************************************************
        * PROBLEM DESCRIPTION: An ABEND04E RC00C90101 can occur at     *
        *                      location DSNIDM.DSNITCUS:5002 when      *
        *                      range partitioning is used by sort for  *
        *                      parallelism.                            *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An ABEND04E RC00C90101 can occur at location DSNITCUS 5002
        (ERQUAL5002) when range partitioning is used by sort for
        parallelism.

        If sort builds a workfile for range partitioning, it saves the
        final workfile in a separate structure, and as a result, it does
        not have the original final workfile pointer at the end of sort.
        If however, the final workfile pointer is available after sort,
        and this is for range partitioning with parallelism, the clean-
        up processing will try to delete this workfile which may no
        longer exist, causing the abend.

        Also, sort needs to correct the counter for the number of
        records in the final workfile if range partitioning is enabled.
        If range partitioning has been enabled, and sort went through
        the merge phase, this counter can double the actual value.
        DB2 sort code has been modified to ensure that the final
        workfile has been cleared if range partitioning is enabled.

        Also, the counter for the number of records for range
        partitioning has been corrected if sort goes through the merge
        phase.

        Additional Keywords: SQLSORT SQLPARALLELISM DB2PARALL/K

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM84388
    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  PM84388
       DSNXSORI  PM84388

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM84388   DSNXSMRE DSNXSORI

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXSMRE
1      DSNXSORI

      LISTEND
 UK92979 COVER LETTER END


 UK92987 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM79757 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS       *
        *                 users of the DB2 stored procedure            *
        *                 SYSPROC.ADMIN_UPDATE_SYSPARM                 *
        ****************************************************************
        * PROBLEM DESCRIPTION: SYSPROC.ADMIN_UPDATE_SYSPARM            *
        *                      incorrectly sets the value of the       *
        *                      subsystem parameter DSN6SYSP.URLGWTH to *
        *                      a thousandth of its correct setting.    *
        ****************************************************************
        * RECOMMENDATION: APPLY PTF                                    *
        ****************************************************************
        SYSPROC.ADMIN_UPDATE_SYSPARM divides the URLGWTH setting by 1000
        since the unit of this parameter is KB. With APAR PM47246,
        (PTF UK74766 for DB2 10 for z/OS, PTF UK74768 for DB2 9 for
        z/OS), this division is no longer required.
        SYSPROC.ADMIN_UPDATE_SYSPARM is modified to correctly set
        subsystem parameter URLGWTH.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM79757
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNADMUZ  PM79757

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM79757   DSNADMUZ

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MACROS
       DSNADMUZ

      LISTEND
 UK92987 COVER LETTER END


 UK93011 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM80971 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS       *
        *                 LOAD utility users                           *
        ****************************************************************
        * PROBLEM DESCRIPTION: Restart of a LOAD utility job results   *
1       *                      in ABENDS0C4 RC4 at DSNUGSUG +x'061A'   *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        Multiple LOAD utilities were to be run from a single job step
        (SYSIN). After executing a LOAD of a large number of partitions
        of a partitioned table space, the next LOAD statement abended
        before serialization was complete in the UTILINIT phase.  Upon
        a RESTART(CURRENT), control blocks were to be rebuilt with
        data from SYSUTILX.  However, a SYSUTILX record was found for a
        control block for the previous LOAD utility that was big enough
        to require an extension SYSUTILX record.  The primary record was
        correctly skipped but the extension record was processed and
        resulted in the ABEND0C4 RC00000004 at DSNUGSUG OFFSET061A.
        LOAD restart processing has been changed to take into account
        the possible existence of an extension record when processing
        for certain control blocks.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM80971
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUGSUG  PM80971
       DSNURWUD  PM80971

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM80971   DSNUGSUG DSNURWUD

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUGSUG
       DSNURWUD

      LISTEND
 UK93011 COVER LETTER END


 UK93023 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM81599 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of utilities       *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNIDBMF ERQUAL501B *
        *                      occurred during a MODIFY RECOVERY       *
        *                      utility concurrently running with a     *
        *                      CHECK DATA utility on the same table    *
        *                      space                                   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        A MODIFY RECOVERY utility was running concurrently with a CHECK
        DATA DELETE YES on the same table space, causing the MODIFY to
1       abend with ABEND04E RC00C90101 at DSNIDBMF:501B. MODIFY RECOVERY
        set UTRW on the target object while CHECK DATA DELETE YES set
        UTUT on the target object.  These two utilities should be
        compatible and should be allowed to execute at the same time.

        The same problem could also happen during a MODIFY RECOVERY,
        MERGECOPY, UNLOAD FROMCOPY or COPYTOCOPY concurrently running
        with some utilities which require exclusive control of the
        target table space or partitions. Instead of abend, UNLOAD
        FROMCOPY would issue MSGDSNU180I - UTILITY IS NOT COMPATIBLE
        WITH THE utility-name UTILITY UTILID=utility-id OBJECT=
        space-name.object-name and end with RC8.
        The DB2 code has been modified to correctly determine which
        utilities that set UTRW and do not access the target object are
        compatible and can execute with utilities that set UTUT and
        require exclusive use of the target object.

        Note that with this APAR fix, the UNLOAD FROMCOPY utility was
        changed to be compatible with other utilities which acquire an
        exclusive state on the target objects.

        Please see the compatibility tables in the Utility Guide and
        Reference for more information on which utilities are
        compatible.

        PM81599 introduces the following changes to the DB2
        documentation:
        UNLOAD UTILITY:
          Compatibility
          The compatibility of the UNLOAD utility and the other
          utilities on the same target objects are shown in the
          following table. If the SHRLEVEL REFERENCE option is
          specified, only SQL read operations are allowed on the same
          target objects; otherwise SQL INSERT, DELETE, and UPDATE are
          also allowed. If the target object is an image copy, INSERT,
          DELETE, and UPDATE are always allowed on the corresponding
          table space. In any case, DROP or ALTER cannot be applied to
          the target object while the UNLOAD utility is running.

          Table 122. Compatibility of UNLOAD with other utilities
          -------------------------------------------------------------
                          UNLOAD        UNLOAD          FROM IMAGE
                          SHRLEVEL      SHRLEVEL        COPY
          Action          REFERENCE     CHANGE
          -------------------------------------------------------------
          CHECK DATA        YES           YES             YES
          DELETE NO
          -------------------------------------------------------------
         |CHECK DATA        NO            NO              YES
          DELETE YES
          -------------------------------------------------------------
          CHECK INDEX       YES           YES             YES
          -------------------------------------------------------------
          CHECK LOB         YES           YES             YES
          -------------------------------------------------------------
          COPY INDEXSPACE   YES           YES             YES
1         -------------------------------------------------------------
          COPY TABLESPACE   YES           YES             YES
          -------------------------------------------------------------
          DIAGNOSE          YES           YES             YES
          -------------------------------------------------------------
          LOAD SHRLEVEL     NO            YES             YES
          CHANGE
          -------------------------------------------------------------
         |LOAD SHRLEVEL     NO            NO              YES
          NONE
          -------------------------------------------------------------
          MERGECOPY         YES           YES             NO
          -------------------------------------------------------------
          MODIFY RECOVERY   YES           YES             NO
          -------------------------------------------------------------
          MODIFY STATISTICS YES           YES             YES
          -------------------------------------------------------------
          QUIESCE           YES           YES             YES
          -------------------------------------------------------------
          REBUILD INDEX     YES           YES             YES
          -------------------------------------------------------------
         |RECOVER(no        NO            NO              YES
          options)
          -------------------------------------------------------------
         |RECOVER ERROR     NO            NO              YES
          RANGE
          -------------------------------------------------------------
         |RECOVER TOCOPY    NO            NO              YES
          or TORBA
          -------------------------------------------------------------
          REORG INDEX       YES           YES             YES
          -------------------------------------------------------------
         |REORG             NO            NO              YES
          TABLESPACE
          UNLOAD
          CONTIUNE or
          PAUSE
          -------------------------------------------------------------
          REORG             YES           YES             YES
          TABLESPACE
          UNLOAD ONLY or
          EXTERNAL
          -------------------------------------------------------------
          REPAIR DUMP or    YES           YES             YES
          VERIFY
          -------------------------------------------------------------
          REPAIR LOCATE     YES           YES             YES
          INDEX PAGE
          REPLACE
          -------------------------------------------------------------
         |REPAIR LOCATE     NO            NO              YES
          KEY or RID DELETE
          or REPLACE
          -------------------------------------------------------------
         |REPAIR LOCATE     NO            NO              YES
          TABLESPACE PAGE
1         REPLACE
          -------------------------------------------------------------
          REPORT            YES           YES             YES
          -------------------------------------------------------------
          RUNSTATS INDEX    YES           YES             YES
          -------------------------------------------------------------
          RUNSTATS          YES           YES             YES
          TABLESPACE
          -------------------------------------------------------------
          STOSPACE          YES           YES             YES
          -------------------------------------------------------------
          Note: If the same data set is used as the output from the
          copy utility and as the input data set of the UNLOAD utility,
          unexpected results can occur.
          -------------------------------------------------------------

        Information about this change 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.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM81599
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNIDBMF  PM81599
       DSNUULIA  PM81599

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM81599   DSNIDBMF DSNUULIA

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIDBMF
       DSNUULIA

      LISTEND
 UK93023 COVER LETTER END


 UK93041 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM77340 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 10 for z/OS who use DSNREXX *
        ****************************************************************
        * PROBLEM DESCRIPTION: A DSNREXX program connected to DB2 with *
        *                      the command CALL SQLDBS 'ATTACH TO'     *
        *                      returns a simple SQLCA on an            *
        *                      ADDRESS DSNREXX 'EXECSQL' command       *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
1       DSNREXX can return the SQLCA in two forms: a set of simple
        variables or a set of compound variables that use the stem
        SQLCA.

        The form of the SQLCA used depends on the version of the
        commands used to interface with DSNREXX.

        When the command CALL SQLDBS 'ATTACH TO' is used to connect to
        DB2, the stem form of the SQLCA should be used in subsequent
        DSNREXX commands.

        Currently, DSNREXX is basing the form of the SQLCA used based
        on the form of the current DSNREXX command.

        DSNREXX should base the form of SQLCA on:
        (1) Default of simple variables
        (2) CALL SQLEXEC results in compound variables (stem form)
        (3) Form is determined by attachment command used
            (a) ADDRESS DSNREXX 'CONNECT' results in simple variables
            (b) CALL SQLDBS 'ATTACH TO' results in compound variables
                (stem form)
        DSNREXX is modified to keep the stem form when
        CALL SQLDBS 'ATTACH TO' is used to connect to DB2.

        In addition, changes to the DB2 documentation will be
        made similar to the following:

        Under Section "Defining the SQL communications area,
        SQLSTATE, and SQLCODE in REXX",
        the following text:
          If you use the ADDRESS DSNREXX "CONNECT" ssid syntax
          to connect to DB2, the SQLCA variables are a set of
          simple variables. If you use the CALL SQLDBS "ATTACH TO"
          syntax to connect to DB2, the SQLCA variables are
          compound variables that begin with the stem SQLCA.

        is changed to the following:

          The SQLCA has the following forms:

              A set of simple variables
              A set of compound variables that begin with the stem SQLCA

          The simple variables is the default form of the SQLCA. Using
          CALL SQLEXEC results in the compound stem variables.
          Otherwise, the attachment command used determines the form of
          the SQLCA. If you use the ADDRESS DSNREXX 'CONNECT' ssid
          syntax to connect to DB2, the SQLCA variables are a set of
          simple variables. If you use the CALL SQLDBS 'ATTACH TO'
          syntax to connect to DB2, the SQLCA variables are compound
          variables that begin with the stem SQLCA.

          Switching forms of the SQLCA within an application is not
          recommended.

        Under section "Accessing the DB2 REXX language support
1       application programming interfaces"

        The SQLDBS and SQLEXEC forms of the DSNREXX commands
        were described as:

          CALL SQLDBS 'ATTACH TO' ssid is equivalent to
          ADDRESS DSNREXX 'CONNECT' ssid.

          CALL 'SQLEXEC' "SQL-statement" is equivalent to
          ADDRESS DSNREXX 'EXECSQL' "SQL-statement".

          CALL SQLDBS 'DETACH' is equivalent to
          ADDRESS DSNREXX 'DISCONNECT'.

        These are changed to the following:

          CALL SQLDBS 'ATTACH TO' ssid is an alternative to
          ADDRESS DSNREXX 'CONNECT' ssid.

          CALL 'SQLEXEC' "SQL-statement" is an alternative to
          ADDRESS DSNREXX 'EXECSQL' "SQL-statement".

          CALL SQLDBS 'DETACH' is an alternative to
          ADDRESS DSNREXX 'DISCONNECT'.

        Keywords:  INCORROUT
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM77340
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DOCUMENTATION:
        The fix for APAR PM77340 has an associated change to the
        DB2 documentation, similar to the following:

        Under Section "Defining the SQL communications area,
        SQLSTATE, and SQLCODE in REXX",
        the following text:
          If you use the ADDRESS DSNREXX "CONNECT" ssid syntax
          to connect to DB2, the SQLCA variables are a set of
          simple variables. If you use the CALL SQLDBS "ATTACH TO"
          syntax to connect to DB2, the SQLCA variables are
          compound variables that begin with the stem SQLCA.

        is changed to the following:

          The SQLCA has the following forms:

              A set of simple variables
              A set of compound variables that begin with the stem SQLCA

          The simple variables is the default form of the SQLCA. Using
          CALL SQLEXEC results in the compound stem variables.
          Otherwise, the attachment command used determines the form of
          the SQLCA. If you use the ADDRESS DSNREXX 'CONNECT' ssid
          syntax to connect to DB2, the SQLCA variables are a set of
1         simple variables. If you use the CALL SQLDBS 'ATTACH TO'
          syntax to connect to DB2, the SQLCA variables are compound
          variables that begin with the stem SQLCA.

          Switching forms of the SQLCA within an application is not
          recommended.

        Under section "Accessing the DB2 REXX language support
        application programming interfaces"

        The SQLDBS and SQLEXEC forms of the DSNREXX commands
        were described as:

          CALL SQLDBS 'ATTACH TO' ssid is equivalent to
          ADDRESS DSNREXX 'CONNECT' ssid.

          CALL 'SQLEXEC' "SQL-statement" is equivalent to
          ADDRESS DSNREXX 'EXECSQL' "SQL-statement".

          CALL SQLDBS 'DETACH' is equivalent to
          ADDRESS DSNREXX 'DISCONNECT'.

        These are changed to the following:

          CALL SQLDBS 'ATTACH TO' ssid is an alternative to
          ADDRESS DSNREXX 'CONNECT' ssid.

          CALL 'SQLEXEC' "SQL-statement" is an alternative to
          ADDRESS DSNREXX 'EXECSQL' "SQL-statement".

          CALL SQLDBS 'DETACH' is an alternative to
          ADDRESS DSNREXX 'DISCONNECT'.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNTZAAA  PM77340

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM77340   DSNTZAAA

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNTZAAA

      LISTEND
 UK93041 COVER LETTER END


 UK93064 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM74891 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of FlashCopy       *
        *                 utilities.                                   *
        ****************************************************************
        * PROBLEM DESCRIPTION: Utilities using FlashCopy experience    *
1       *                      FlashCopy failures, but updates to      *
        *                      SYSCOPY are successful.  Successful     *
        *                      final return codes are received for     *
        *                      utility jobs with FlashCopy errors.     *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
          Various problems have been reported with error handling
        involving utilities using FlashCopy processing.  Specifically,
        when COPY or REORG utilities request FlashCopies, in some
        cases errors received on individual data sets during FlashCopy
        processing have not been reflected properly in the final
        results of the jobs.  In some instances jobs which should
        have received a final return code of RC8 got RC4 or RC0 instead.
        At other times a record was inserted into SYSIBM.SYSCOPY
        indicating a successful FlashCopy had been made when it had not.
        The precise symptoms of the problem, and whether it occurred at
        all, is unpredicatable because it is dependent on a number of
        factors, including what utility is running and what keywords are
        specified for it, the number of objects being operated on by
        the utility, what kind of objects they are, and the order in
        which they are specified or included in a LISTDEF.  Similar
        issues could also occur for LOAD and REBUILD INDEX utilities
        if they request FlashCopies.
          These anomalies are due to inconsistencies in the way
        errors and return codes are propogated from DFSMSdss to DB2
        and also within DB2 utility code.
          Code was changed to better handle FlashCopy errors
        received and passed back to DB2 when FlashCopy is requested
        for COPY, REORG, LOAD, or REBUILD INDEX utilities.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM74891
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUBBFC  PM74891
       DSNUGFCD  PM74891
       DSNUGFUM  PM74891
       DSNUGULM  PM74891
       DSNUGUTC  PM74891

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM74891   DSNUBBFC DSNUGFCD DSNUGFUM DSNUGULM DSNUGUTC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUBBFC
       DSNUGFCD
       DSNUGFUM
       DSNUGULM
       DSNUGUTC

      LISTEND
1UK93064 COVER LETTER END


 UK93078 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM76865 -
        ****************************************************************
        * USERS AFFECTED: All DB2 V10 users.                           *
        ****************************************************************
        * PROBLEM DESCRIPTION: DB2 data sharing member restart failure *
        *                      MSGDSNT384I issued by DB2 for timeout   *
        *                      doing restart.                          *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        DB2 zparm IRLMSID may be incorrectly entered which could be
        different than IRLMNM in the irlm startup proc that is started
        by DB2. This may result in failure to identify to correct IRLM
        followed by DB2 restart timeout and ABND=04E-00E30081. Message
        DSNT384I is also issued. From messages, it is not clear which
        IRLM subsystem was being started.
        Need a new message to indicate IRLM subsystem id for the IRLM
        which is restarted with DB2 auto-restart.
        A new message DSNT820I is being introduced with this APAR to
        identify the IRLM subsystem id (IRLMSID) which is going to be
        started by DB2 auto-restart.

        DB2 Messages book will be adding following documentation:

        DSNT820I

        DB2 IS STARTING IRLM SUBSYSTEM=irlm_id

        Explanation:
          DB2 auto-restart is attempting to automatically start IRLM
          with IRLM subsystem name as set in IRLMSID in the DSNZPARM
          used at the startup.

          irlm_id = IRLM subsystem ID set in macro DSN6SPRM which was
          in the DSNZPARM

        System action:
          none

        Operator response:
          none.

        System programmer response:
          none

        Problem determination:
         IRLMNM parm given in the IRLM startup procedure (IRLMPRC in
         DSNZPARM) should be the same as IRLMSID in the DSNZPARM used
         at startup. If DB2 restart had failed, please refer to the
         documentation for DSNT384I.
    COMPONENT:  5740-XYR00-HDBAA10
1   APARS FIXED: PM76865
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNFMDIR  PM76865
       DSNFTDIR  PM76865
       DSNTLIDE  PM76865

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM76865   DSNFMDIR DSNFTDIR DSNTLIDE

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNFMDIR
       DSNFTDIR
       DSNTLIDE

      LISTEND
 UK93078 COVER LETTER END


 UK93083 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM84587 -
        ****************************************************************
        * USERS AFFECTED: All IRLM220(HIR2220) and IRLM230(HIR2230)    *
        *                 users.                                       *
        ****************************************************************
        * PROBLEM DESCRIPTION: IRLM ESTAE recovery could be delayed by *
        *                      30 seconds, after DB2/IMS or IRLM is    *
        *                      abnormally terminated.                  *
        ****************************************************************
        * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
        ****************************************************************
        IRLM ESTAE in DXRRL070 has a timer to wait for 30 seconds to
        allow any active request SRBs scheduled to DBMS Exits to be
        completed before it returns to RTM. Due to an error in IRLM
        SRB termination recovery routine, IRLM may not correctly
        decrement active request counts and may not post termination ECB
        (RLMTMECB) to the ESTAE routine. This could result in IRLM ESTAE
        waiting 30 seconds before it posts the RLMTMECB and continues
        termination.  If DB2 or IMS attempt to restart within 30 seconds
        after termination, it may fail if the previous instance of IRLM
        has not completed its termination.
        This APAR fixes IRLM SRB termination recovery code to correctly
        decrement active request counts for DBMS Exit drives.  When the
        count of SRBs scheduled to Status Exit drive goes to zero, IRLM
        termination ECB (RLMTMECB) is posted to the wait in the ESTAE
        routine timely and avoids the 30 second wait.  This fix will
        also reschedule complete SRBs correctly to IRLM for Notify,
        P-Lock, Deadlock and Timeout Exit processing.
    COMPONENT:  5695-16401-HIR2230
    APARS FIXED: PM84587
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
       DXRRL060  PM84587

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM84587   DXRRL060

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DXRRL060

      LISTEND
 UK93083 COVER LETTER END


 UK93116 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM83857 -
        ****************************************************************
        * USERS AFFECTED: Users of DB2 10 for z/OS EXPLAIN             *
        ****************************************************************
        * PROBLEM DESCRIPTION: When using DB2 for z/OS EXPLAIN, the    *
        *                      output in NODE_DATA column of           *
        *                      DSN_QUERY_TABLE may not be correct      *
        *                      when the query contains a common table  *
        *                      expression (CTE) and the CTE contains   *
        *                      columns in an ORDER BY clause that are  *
        *                      not in the SELECT clause.               *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When using DB2 for z/OS EXPLAIN, the output in NODE_DATA column
        of DSN_QUERY_TABLE may not be correct when the query contains a
        common table expression (CTE) and the CTE contains columns in an
        ORDER BY clause that are not in the SELECT clause.

        An example that demonstrates the problem:

          CREATE TABLE T1 (C1 INT, C2 VARCHAR(2));

          EXPLAIN ALL SET QUERYNO=1 FOR
          WITH MYTABLE (Z1) AS
            (SELECT C1
             FROM T1
             ORDER BY C2)    <= C2 is in ORDER BY but not in SELECT
          SELECT Z1
          FROM MYTABLE;

        Additional Keywords:
        SQLEXPLAIN SQLCTE SQLORDERBY
        DB2 code is now changed to correctly output the text to
        NODE_DATA column of DSN_QUERY_TABLE for this scenario.
1   COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM83857
    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  PM83857

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM83857   DSNXODTX

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXODTX

      LISTEND
 UK93116 COVER LETTER END


 UK93117 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM79265 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 for z/OS who use scrollable *
        *                 cursors and FETCH FIRST n ROWS ONLY          *
        ****************************************************************
        * PROBLEM DESCRIPTION: An asensitive scrollable cursor         *
        *                      defined with FETCH FIRST n ROWS ONLY    *
        *                      can get SQLCODE -243                    *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An asensitive scrollable cursor defined with the FETCH FIRST
        n ROWS ONLY clause may get SQLCODE -243.  An asensitive
        cursor should be as sensitive as possible.  If the FETCH
        FIRST n ROWS ONLY clause is on the outermost fullselect,
        then the cursor cannot be SENSITIVE DYNAMIC.  In this situation,
        the asensitive cursor should become INSENSITIVE.

        Additional Keywords:
        SQLCODE243 SQLASENSITIVE SQLSCROLL SQLFFNR
        The documentation states that the FETCH FIRST n ROWS ONLY clause
        cannot be specified in the outermost fullselect of a sensitive
        dynamic scrollable cursor.  Therefore, code is changed to allow
        an asensitive scrollable cursor with FETCH FIRST n ROWS ONLY
        defined in the outermost fullselect to be treated as
        INSENSITIVE instead of getting SQLCODE -243.
        There may be some performance degradation if the cursor did
        not receive -243 before and this fix is now applied to
        interpret the asensitive cursor as INSENSITIVE.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM79265
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
1                LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        A rebind is necessary for static applications to rebuild
        access paths based on changes in this APAR.

        PM79265 corrects a problem where an asensitive scrollable
        cursor defined with FETCH FIRST n ROWS ONLY in the outermost
        fullselect gets SQLCODE -243.

        To make this fix effective for a static application, it must 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 PM57420:

        A rebind is necessary for static applications to rebuild
        access paths based on changes in this APAR.

        PM57420 corrects a problem where lock avoidance is being
        used for a singleton, non-cursor SELECT when ISOLATION(CS)
        is used with CURRENTDATA(YES).  Concurrent updates may yield
        inconsistent results for the SELECT.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM56626:

        See PM56626 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM56626 allows users to define a dynamic scroll cursor whose
        SELECT statment contains a subquery such that the base object
        of the outer subselect, and of the subquery, is the same, but
        with the conditions that (1) FOR FETCH ONLY is specified in
        the SELECT statement, and (2) the base object is accessed via
        the index to avoid any sort or materialization.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM51623:

        A rebind is necessary to rebuild package and/or plan structures
        based on the changes in this APAR.

        PM51623 corrects a problem that an inefficient access path may
        be chosen for a DELETE statement against a VIEW on which an
        INSTEAD OF DELETE trigger is defined.

        To make this fix effective for a static application, it must be
1       rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM30690:

        See PM30690 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM30690 corrects a problem of an infinite loop for a MERGE
        statement with update.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOGPS  PM79265

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM79265   DSNXOGPS

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOGPS

      LISTEND
 UK93117 COVER LETTER END


 UK93125 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM81000 -
        ****************************************************************
        * USERS AFFECTED: DB2 for z/OS users whose queries contain     *
        *                 a subquery, and parallelism is enabled.      *
        ****************************************************************
        * PROBLEM DESCRIPTION: The I/O and CPU can be inaccurately     *
        *                      estimated for a parent query block      *
        *                      table of a query during hybrid join,    *
        *                      which may result in an inefficient      *
        *                      access path when parallelism is         *
        *                      enabled.                                *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The I/O and CPU of a parent query block table in hybrid join
        can be inaccurately estimated, and this may result in an
        inefficient access path when parallelism is enabled.

        Additional Keywords:
        SQLACCESSPATH SQLPERFORMANCE SQLHYBRID SQLHYBRIDJOIN HYBRIDJOIN
        SQLPARALLELISM PARALLELISM DB2PARALL/K

1       Code is changed to correct the I/O and CPU estimation
        for the situation described above.  DB2 will have a better
        chance to choose more efficient access paths for these
        types of queries.  As with any change to DB2 query
        optimization that can drive a different access path,
        there is some risk of query performance regression.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM81000
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM81000:

        A rebind is necessary for static applications to rebuild
        access paths based on changes in this APAR.

        PM81000 corrects a problem of inaccurately estimated I/O and
        CPU of a parent query block table in hybrid join when
        parallelism is enabled.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOCSH  PM81000

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM81000   DSNXOCSH

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOCSH

      LISTEND
 UK93125 COVER LETTER END


 UK93150 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM83997 -
        ****************************************************************
        * USERS AFFECTED: Users of DB2 for z/OS executing a            *
        *                 BIND PACKAGE COPY command using              *
        *                 APCOMPARE.                                   *
        ****************************************************************
        * PROBLEM DESCRIPTION: THE PROBLEM THIS FIX ADDRESSES HAS THE  *
        *                      FOLLOWING REPORTED SYMPTOMS:            *
        *                                                              *
        *                         DSNT285I -DBXX DSNTBCM2              *
        *                         BIND PACKAGE = <package>             *
        *                          <x> STATEMENTS WHERE COMPARISON     *
        *                       COULD NOT BE PERFORMED.                *
1       *                                                              *
        *                                                              *
        *                      PROBLEM SCENARIO:                       *
        *                                                              *
        *                      The reported error occurred when        *
        *                      attempting a BIND PACKAGE COPY on       *
        *                      an existing package with APCOMPARE      *
        *                      after a precompile. This can also       *
        *                      affect BIND PACKAGE DEPLOY with         *
        *                      APCOMPARE.                              *
        *                                                              *
        *                      Here is an example:                     *
        *                                                              *
        *                       Case1 - Comparison OK                  *
        *                       1.Create a new program (precompile     *
        *                         and link edit)                       *
        *                       2.BIND PACKAGE(XX) MEMBER(YY)          *
        *                         APCOMPARE(WARN)                      *
        *                       3.BIND PACKAGE(ZZ) COPY(XX.YY)         *
        *                         APCOMPARE(WARN)                      *
        *                                                              *
        *                       Case2 - Comparison OK                  *
        *                       1.BIND PACKAGE(XX) MEMBER(YY)          *
        *                         APCOMPARE(WARN)                      *
        *                       2.BIND PACKAGE(ZZ) COPY(XX.YY)         *
        *                         APCOMPARE(WARN)                      *
        *                                                              *
        *                       Case3 - Doesn't compare                *
        *                       1.Precompile the program, but          *
        *                         no change in SQL.                    *
        *                       2.BIND PACKAGE(XX) MEMBER(YY)          *
        *                         APCOMPARE(WARN)                      *
        *                       3.BIND PACKAGE(ZZ) COPY(XX.YY)         *
        *                         APCOMPARE(WARN)                      *
        *                                                              *
        *                      Case 3 BIND COPY gets this error:       *
        *                                                              *
        *                      =>DSNT285I  -DBXX DSNTBBP2 BIND FOR     *
        *                           PACKAGE = DB2.XX.YY,               *
        *                       USE OF APCOMPARE RESULTS IN:           *
        *                        0 STATEMENTS WHERE COMPARISON IS      *
        *                          SUCCESSFUL                          *
        *                        0 STATEMENTS WHERE COMPARISON IS      *
        *                          NOT SUCCESSFUL                      *
        *                        2 STATEMENTS WHERE COMPARISON         *
        *                          COULD NOT BE PERFORMED.             *
        *                                                              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        SUMMARY OF DB2 EVENTS:
        DB2 uses contoken as one of the search criteria to find the
        previous access path to do the comparison for APCOMPARE. Because
        the contoken changed with the precompile, DB2 used the wrong
        contoken variable to do the comparison. This comparison
        failed.
1       PROBLEM CONCLUSION:
        DB2 has been fixed to point to the correct variable when
        searching for the previous access path to do the APCOMPARE.

        ADDITIONAL KEYWORDS:
        BIND COPY DEPLOY APCOMPARE MSGDSNT285I
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM83997
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNTBCM2  PM83997

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM83997   DSNTBCM2

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNTBCM2

      LISTEND
 UK93150 COVER LETTER END


 UK93153 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM73758 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of the RECOVER     *
        *                 utility with the BACKOUT YES option -or-     *
        *                 users of FlashCopy image copies (FCIC).      *
        ****************************************************************
        * PROBLEM DESCRIPTION: This APAR addresses two issues:         *
        *                      1. ABEND04E RC00D1032A in DSNJR003      *
        *                         and ABEND04E RC00E40106 in DSNUCALC  *
        *                         during RECOVER utility with the      *
        *                         BACKOUT YES option.                  *
        *                      2. Extraneous ICF Catalog Search        *
        *                         Interface (CSI) invocation during    *
        *                         the creation of FCICs by COPY,       *
        *                         REORG, LOAD, or REBUILD INDEX        *
        *                         utilities.                           *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The two issues addressed by this APAR are:
        1. ABEND04E RC00D1032A in DSNJR003 and ABEND04E RC00E40106
           in DSNUCALC during RECOVER utility with the BACKOUT YES
           option.
           ..
           MsgDSNJ113E RBA '000000000000' NOT IN ANY ACTIVE OR ARCHIVE
           LOG DATA SET is issued to the console.
           ..
1          MsgDSNU1550I LOGCSR IS STARTED FOR MEMBER PRIOR CHECKPOINT
           RBA = X'000000000000' is issued to the job output.
           ..
           These abends occur when the recovery point identified by
           TOLOGPOINT or TORBA is not contained within the most
           recent DB2 system checkpoints that are recorded in the BSDS
           for each member.  In this case, RECOVER BACKOUT YES cannot
           proceed, because the checkpoint RBA that is prior to the
           recovery point for each member is required for backout
           processing.
           ..
           Additional keywords: DSNJ113E DSNU1550I
           ..
        2. During the creation of FCICs by the COPY, REORG, LOAD,
           or REBUILD INDEX utilities, the ICF Catalog Search
           Interface (CSI) is invoked to check if the FCIC data set
           is a duplicate.  This check is not necessary because the
           information in catalog table SYSIBM.SYSCOPY is used to
           check and prevent duplicate image copy data sets.
        1. A new error message, MsgDSNU1545I, is issued when the
           recovery point for RECOVER BACKOUT YES is not contained
           within the most recent DB2 system checkpoints in the BSDS
           for each member.
           ..
           Documentation change to the DB2 Messages manual:

            DSNU1545I csect-name RECOVER WITH BACKOUT YES CANNOT
                      PROCEED.  THE RECOVERY POINT IS OLDER THAN
                      THE EARLIEST CHECKPOINT IN THE BSDS.
            Explanation: The recovery point that is identitied by
                         TOLOGPOINT or TORBA is not contained within
                         the most recent DB2 system checkpoints that
                         are recorded in the BSDS for each member.
                         RECOVER with the BACKOUT YES option cannot
                         proceed, because the checkpoint RBA that is
                         before the recovery point for each member is
                         required for backout processing.
            csect-name:  The name of the control section that issued
                         the message.
            System action: The RECOVER utility ends with return code 8
                         and does not process any of the objects.
                         The objects are left in the state that they
                         were in before the RECOVER operation.
            System programmer response: Remove the BACKOUT YES option
                         and resubmit the RECOVER job.  This revised
                         job recovers the objects to the same point
                         in time. However, the data is recovered by
                         using a recovery base and applying the logs
                         rather than using backout processing.
            Recommendation: Use the output from the REPORT utility
                         with the RECOVERY option for all of the
                         objects to ensure that a valid recovery
                         base exists before you run RECOVER.
            Severity: 8 (error)
          ..
          Documentation change to the Utility Guide and Reference
1         manual, Chapter 23 RECOVER utility.  A new paragraph is
          added under the BACKOUT YES option:
            If you specify BACKOUT YES, the recovery point must be
            within the most recent DB2 system checkpoints that are
            recorded in the BSDS for each member. Otherwise, the
            recovery cannot proceed and returns an error.
          ..
        2. The CSI invocation issued during the check for duplicate
           FCICs has been removed in the COPY, REORG, LOAD, and
           REBUILD INDEX utilities.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM73758
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DOCUMENTATION:
        The PTF for APAR PM73758 adds a new error message that will be
        issued by the RECOVER utility with the BACKOUT YES option
        when the recovery point is not contained within the most
        recent DB2 system checkpoints that are recorded in the BSDS
        for each member.
        ..
        Documentation change to the DB2 Messages manual:

            DSNU1545I csect-name RECOVER WITH BACKOUT YES CANNOT
                      PROCEED.  THE RECOVERY POINT IS OLDER THAN
                      THE EARLIEST CHECKPOINT IN THE BSDS.
            Explanation: The recovery point that is identitied by
                         TOLOGPOINT or TORBA is not contained within
                         the most recent DB2 system checkpoints that
                         are recorded in the BSDS for each member.
                         RECOVER with the BACKOUT YES option cannot
                         proceed, because the checkpoint RBA that is
                         before the recovery point for each member is
                         required for backout processing.
            csect-name:  The name of the control section that issued
                         the message.
            System action: The RECOVER utility ends with return code 8
                         and does not process any of the objects.
                         The objects are left in the state that they
                         were in before the RECOVER operation.
            System programmer response: Remove the BACKOUT YES option
                         and resubmit the RECOVER job.  This revised
                         job recovers the objects to the same point
                         in time. However, the data is recovered by
                         using a recovery base and applying the logs
                         rather than using backout processing.
            Recommendation: Use the output from the REPORT utility
                         with the RECOVERY option for all of the
                         objects to ensure that a valid recovery
                         base exists before you run RECOVER.
            Severity: 8 (error)
        ..
        Documentation change to the Utility Guide and Reference
        manual, Chapter 23 RECOVER utility.  A new paragraph is
        added under the BACKOUT YES option:
1         If you specify BACKOUT YES, the recovery point must be
          within the most recent DB2 system checkpoints that are
          recorded in the BSDS for each member. Otherwise, the
          recovery cannot proceed and returns an error.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNFMDIR  PM73758
       DSNFUDRE  PM73758
       DSNUBCKD  PM73758
       DSNUCALA  PM73758
       DSNUGFCB  PM73758
       DSNUMSGE  PM73758

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM73758   DSNFMDIR DSNFUDRE DSNUBCKD DSNUCALA DSNUGFCB DSNUMSGE

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNFMDIR
       DSNFUDRE
       DSNUBCKD
       DSNUCALA
       DSNUGFCB
       DSNUMSGE

      LISTEND
 UK93153 COVER LETTER END


 UK93162 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM71067 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS parallelism users.       *
        ****************************************************************
        * PROBLEM DESCRIPTION: Parallel thread cannot be cancelled.    *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        DB2 parallel thread cannot be cancelled. After CANCEL
        command is issued, DB2 parallel thread is falling into
        an infinite loop.
        The problem is inside DB2 parallelism processing logic.
        In certain loops there are no checks for the CANCEL command.
        So, after CANCEL command has been issued, DB2 continues to
        run without realization of the CANCEL status of the thread.
        This is not SQL statement specific, and it could happen on
        any queries running in parallel mode.
        DB2 has been fixed to check CANCEL status during parallel
        processing loop so that DB2 will not fall into infinite
        loop after CANCEL command is issued.

        Additional Keywords: PARALLELISM  SQLPARALLELISM
                             DB2PARALL/K  SQLCPUP

1   COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM71067
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXPSRD  PM71067

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM71067   DSNXPSRD

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXPSRD

      LISTEND
 UK93162 COVER LETTER END


 UK93187 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM77006 -
        ****************************************************************
        * USERS AFFECTED: ALL DB2 10 and 9 for z/OS users.             *
        ****************************************************************
        * PROBLEM DESCRIPTION: SQLCODE551 received when a user with    *
        *                      DBADM authority with grant option on    *
        *                      DSNDB04 tried to grant select privilege *
        *                      on a table in an implicit database.     *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        SQLCODE551 was received when a user with DBADM authority with
        grant option on DSNDB04 tried to grant select privilege on a
        table that he created for another user in an implicit database.

        SQLCODE551 can also be received while using DBADM authority
        with grant option on DSNDB04 for granting other table
        privileges on a table in an implicit database.

        Authorization did not take into consideration the grantor
        having DBADM authority with grant option on DSNDB04 during the
        grants on a table in an implicit database.
        DB2 code is changed to allow a user with DBADM on DSNDB04
        with grant option to be able to perform grants in the above
        stated scenarios.

        Additional keywords: DBADM SQLCODE551 GRANT
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM77006
    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
       DSNXA2TM  PM77006

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM77006   DSNXA2TM

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXA2TM

      LISTEND
 UK93187 COVER LETTER END


 UK93191 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM81417 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS       *
        *                 utility users of DSN1PRNT using keyword      *
        *                 FORMAT                                       *
        ****************************************************************
        * PROBLEM DESCRIPTION: DSN1PRNT specifying the FORMAT option   *
        *                      may invalidly set a RC4 and issue the   *
        *                      following messages:                     *
        *                      *** DATA PAGE - INVALID HOLE/RECORD     *
        *                          LENGTH -UNABLE TO FORMAT PAGE       *
        *                      *** PAGE IN ERROR - FORMATTED CONTENTS  *
        *                          MAY BE INCONSISTENT OR TRUNCATED    *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When the FORMAT parameter is specified, DSN1PRNT formats the
        input data set.

        When processing a data page, DSN1PRNT may treat a RID value
        as a length value. If that value does not fit within the
        page, then DSN1PRNT sets a RC=4 and prints the following
        messages:

          *** DATA PAGE - INVALID HOLE/RECORD LENGTH
              -UNABLE TO FORMAT PAGE ***
          ***  PAGE IN ERROR - FORMATTED CONTENTS MAY BE INCONSISTENT
               OR TRUNCATED
        DSN1PRNT is modified to no longer treat the RID value as a
        length value.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM81417
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSN1DFPG  PM81417

1     CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM81417   DSN1DFPG

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSN1DFPG

      LISTEND
 UK93191 COVER LETTER END


 UK93202 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM74904 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of an SQL          *
        *                 statement that contains a recursive common   *
        *                 table expression with a LOB expression in    *
        *                 the SELECT list.                             *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C4 PIC11 at the location          *
        *                      DSNIDM DSNOPUFF OFFSET02BA could happen *
        *                      for an SQL statement that contains a    *
        *                      recursive common table expression with  *
        *                      a LOB expression in the SELECT list.    *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An example is shown below:

        CREATE TABLE T1(C1 INTEGER, LOB_COL CLOB(10));

         WITH CTE(C1, LOB_C2) AS
         (
            SELECT 1, LOB_COL || 'A'
            FROM T1
           UNION ALL
            SELECT C1+1, LOB_C2 || 'B'
            FROM CTE
            WHERE C1+1 < 10
         )
         SELECT * FROM T1 LEFT OUTER JOIN CTE
                           ON T1.C1= CTE.C1
         ;

        DB2 did not correctly process the aforementioned SQL statements,
        which caused the ABEND.
        DB2 has been modified to correctly process the aforementioned
        SQL statement, so there will be no ABEND.

        Additional keywords: SQLCTE SQLLOB
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM74904
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
1                LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        See PM74904 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM74904 corrects a problem that ABEND0C4 PIC11 at the
        location DSNIDM DSNOPUFF OFFSET02BA could happen for an SQL
        statement that contains a recursive common table expression with
        a LOB expression 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.

        With this APAR applied, more storage will be used to store LOB
        values for the recursive common table expression.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNOTFLA  PM74904
       DSNXOSL   PM74904

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM74904   DSNOTFLA DSNXOSL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNOTFLA
       DSNXOSL

      LISTEND
 UK93202 COVER LETTER END


 UK93217 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM81291 -
        ****************************************************************
        * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
        *                 Specifically those where DB2 is accessed     *
        *                 as a server via TCP/IP connections and       *
        *                 Enterprise WorkLoad Manager (EWLM)           *
        *                 services are being utilized.                 *
        ****************************************************************
        * PROBLEM DESCRIPTION: Periodic DSNL044I messages issued       *
        *                      from DSNLIRTR indicating MVS macro      *
        *                      IWMESTOP or IWMESTRT failed with        *
        *                      RETCODE='00000008'X and                 *
        *                      RSNCODE='00000896'X.                    *
        *                      Users may also observe abend            *
        *                      0C4-00000004 DSNLIRTR+25E2.             *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Since the initial implementation by DB2 to support the
1       Enterprise Workload Manager (EWLM) services monitoring
        support, various enhancements to DB2 9 and beyond, and in
        particular the enhanced support for AMODE(64), have caused
        the EWLM invocation environment to be setup incorrectly.
        In particular, the EWLM service macros, IWMESTRT and IWMESTOP,
        (in the manner used by DB2) require the macros be invoked from
        AMODE(31) environments.  When the AMODE(31) macro invocation
        environment is not setup correctly, an EWLM request may result
        in a return code of 8 and a reason code '0896'X being reported
        by DB2 message DSNL042I.  This return and reason code
        combination is returned by an EWLM request when one or more of
        the parameters passed on the macro invocation is invalid.
        Users may also observe abend 0C4-00000004 DSNLIRTR+25E2.

        DB2 9 and beyond have been changed to correctly setup the
        EWLM macro invocation environment to prevent errors when
        invoking EWLM services.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM81291
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNLCAIA  PM81291
       DSNLCRNC  PM81291
       DSNLCRTD  PM81291
       DSNLCTRC  PM81291
       DSNLIRTR  PM81291
       DSNLQCTL  PM81291
       DSNLQINA  PM81291
       DSNLTACC  PM81291

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM81291   DSNLCAIA DSNLCRNC DSNLCRTD DSNLCTRC DSNLIRTR DSNLQCTL
                 DSNLQINA DSNLTACC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNLCAIA
       DSNLCRNC
       DSNLCRTD
       DSNLCTRC
       DSNLIRTR
       DSNLQCTL
       DSNLQINA
       DSNLTACC

      LISTEND
 UK93217 COVER LETTER END


 UK93224 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM84539 -
1       ****************************************************************
        * USERS AFFECTED: Users of an external SQL PL stored procedure *
        *                 or a C/C++ application that contains a large *
        *                 SQL statement with a question mark (?) or    *
        *                 back slash (\) inside a literal string with  *
        *                 DB2 for z/OS Version 9.1 or 10.1.            *
        ****************************************************************
        * PROBLEM DESCRIPTION: DB2 may incorrectly issue SQLCODE -199  *
        *                      or -104 during the bind of a large SQL  *
        *                      statement from an external SQL PL       *
        *                      stored procedure or a C/C++             *
        *                      application when the SQL statement has  *
        *                      a string containg a question mark (?)   *
        *                      or a back slash (\) and one of these    *
        *                      two characters is beyond the position   *
        *                      32767 in the SQL statement.             *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The following example may expose the problem:
        EXEC SQL
          DECLARE CURSOR1 CURSOR WITH RETURN FOR
          SELECT 1 AS C1, 2 AS C2,
          ......
          UNION SELECT 1000 AS C1000, 1001 AS C1001,
          '~/Reports/frmSchool.aspx?type=school' AS C1002 FROM T1000;

        The above SQL statement is embedded in a C application and the
        position of the literal string is beyond 32767 in the SQL
        statement.

        Additional keywords: SQLCODE199 SQLCODE104 SQLEXTERNALSQLPL
                             SQLSP SQLSTOREDPROC
        DB2 for z/OS code is changed so that the invalid error is
        no longer reported.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM84539
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNHTOKR  PM84539

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM84539   DSNHTOKR

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNHTOKR

      LISTEND
 UK93224 COVER LETTER END


1UK93229 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM80852 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS       *
        *                 users of ONLINE REORG utility against        *
        *                 PBG table space with APPEND attribute.       *
        ****************************************************************
        * PROBLEM DESCRIPTION: After running REORG with SHRLEVEL       *
        *                      CHANGE or REFERENCE on a PBG table      *
        *                      space with  APPEND YES attribute,       *
        *                      the subsequent rows are inserted to     *
        *                      the cached last partition of the        *
        *                      table space. The reclaimed spaces       *
        *                      prior to the cached last partition      *
        *                      during the REORG were not reused.       *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Since PBG table with APPEND attribute indicates data rows are
        inserted to the end of table,  the last partition of the table
        space is cached during the insert transaction. When insert
        transaction is running concurrently with ONLINE REORG on a PBG
        table with APPEND YES attribute, REORG can reclaim space and
        leave empty partition(s) towards at the end of table space.
        However, the cached last partitioned number from prior insert
        transaction  was not reset during REORG and subsequent
        inserted rows are inserted to the last cached partition.
        As a result, reclaimed space in the empty partitions prior to
        the cached last partition may not be reused and further causes
        the growth of table space.
        DB2 code has been modified to set the right starting partition
        after the table space's closed.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM80852
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNIPPHC  PM80852

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM80852   DSNIPPHC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIPPHC

      LISTEND
 UK93229 COVER LETTER END


 UK93238 COVER LETTER START
    PROBLEM DESCRIPTION(S):
1     PM83184 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS RUNSTATS utility users   *
        *                 collecting statistics using TABLESAMPLE      *
        *                 SYSTEM.                                      *
        ****************************************************************
        * PROBLEM DESCRIPTION: INCORROUT in MSGDSNU613I, MSGDSNU624I   *
        *                      MSGDSNU614I, SYSIBM.SYSTABLEPART,       *
        *                      SYSIBM.SYSTABSTATS and SYSIBM.SYSTABLES *
        *                      showing incorrect PERCACTIVE and        *
        *                      PCTROWCOMP statistics.                  *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        When an user executed RUNSTATS TABLESPACE TABLESAMPLE SYSTEM n,
        the utility reported incorrect PERCACTIVE and PCTROWCOMP
        statistics and updated the catalog tables with those statistics.

        The incorrect PERCACTIVE were reported in DSNU613I and the
        values were updated in SYSTABLEPART.

        The incorrect PCTROWCOMP was reported in DSNU624I and
        DSNU614I and the values were updated in SYSTABSTATS
        and SYSTABLES catalog tables.

        The PERCACTIVE and PCTROWCOMP values were incorrectly computed
        as some intermediate values were used without taking into
        consideration the sampling rate employed.
        Code was modified to correctly estimate the PERCACTIVE and
        PCTROWCOMP statistics when TABLESAMPLE SYSTEM is specified.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM83184
    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  PM83184
       DSNUSUPT  PM83184
       DSNUSUTB  PM83184

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM83184   DSNUSEF2 DSNUSUPT DSNUSUTB

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUSEF2
       DSNUSUPT
       DSNUSUTB

      LISTEND
 UK93238 COVER LETTER END


 UK93245 COVER LETTER START
1   PROBLEM DESCRIPTION(S):
      PM81976 -
        ****************************************************************
        * USERS AFFECTED: All HIR2220 (IRLM2.2) and HIR2230 (IRLM2.3)  *
        *                 users of data sharing SYSPLEXDS.             *
        ****************************************************************
        * PROBLEM DESCRIPTION: IRLM failed to respond to the rebuild   *
        *                      quiesce event of the lock structure     *
        *                      causing the whole sysplex hung with     *
        *                      message IXL040E and ABEND=S026 with     *
        *                      REASON=08118001                         *
        ****************************************************************
        * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
        ****************************************************************
           A co-exist rebuild is triggered during IRLM Global Initial-
        ization Process. If there are Failed Connection events then
        these FailConn events need to be processed before the Rebuild
        Quiesce event.  The rebuild QE will be saved in the Suspend SRB
        Communication Area.

           After finishing with the FailConn events, the rebuild QE is
        left untouched in the SCA.  Without responding to the Rebuild
        Quiesce event, the rebuild process for the lock structure can
        not continue.  XES issues message IXL040E and then abends S026
        with reason = 08118001.

        GEN:
        KEYWORDS:

        *** END IMS KEYWORDS ***
           Logic is added to re-queue the rebuild QE after processing
        the last FailConn QE.

    COMPONENT:  5695-16401-HIR2230
    APARS FIXED: PM81976
    SPECIAL CONDITIONS:
      COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DXRRL2E0  PM81976
       DXRRL2E1  PM81976
       DXRRL2U0  PM81976
       DXRRL2V0  PM81976
       DXRRL210  PM81976

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM81976   DXRRL2E0 DXRRL2E1 DXRRL2U0 DXRRL2V0 DXRRL210

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DXRRL2E0
       DXRRL2E1
       DXRRL2U0
       DXRRL2V0
1      DXRRL210

      LISTEND
 UK93245 COVER LETTER END


 UK93249 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM82406 -
        ****************************************************************
        * USERS AFFECTED: DB2 10 for z/OS users of queries with LIKE   *
        *                 predicates containing host variables and     *
        *                 in a package bound with option               *
        *                 REOPT(ALWAYS)                                *
        ****************************************************************
        * PROBLEM DESCRIPTION: DB2 may select an inefficient access    *
        *                      path for a query with a LIKE predicate  *
        *                      if the LIKE predicate contains a host   *
        *                      variable and the query is in a package  *
        *                      bound with the option REOPT(ALWAYS).    *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        DB2 may produce an inaccurate estimation of the index matching
        filter factor if the following conditions are satisfied:

        1. There is a LIKE predicate in the query and the LIKE predicate
        is selected as a matching predicate of the index;

        2. The LIKE predicate contains a host variable;

        3. The query is in a package bound with the option REOPT(ALWAYS)
        and a literal starting with a wildcard is passed to the host
        variable at execution time.

        For example,

        SELECT *
        FROM T1
        WHERE C1 LIKE :HV1;

        The above query is in a package bound with REOPT(ALWAYS). There
        is an index IX1 defined on C1. If the literal passed to HV1 at
        execution time is '%AAAAAAAAAAA', the matching filter factor
        of the index IX1 may be inaccurately estimated. Consequently,
        DB2 may select an inefficient access path for this query.

        Additional Keywords:
        SQLPERFORMANCE SQLACCESSPATH SQLLIKE SQLHOSTVAR REOPT
        Code has been modified to produce an accurate index matching
        filter factor for the cases described as above.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM82406
    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
       DSNXODFB  PM82406
       DSNXOGBM  PM82406

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM82406   DSNXODFB DSNXOGBM

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXODFB
       DSNXOGBM

      LISTEND
 UK93249 COVER LETTER END


 UK93300 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM81692 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 10 for z/OS who use         *
        *                 partitioned tables partitioned by TIMESTAMP  *
        ****************************************************************
        * PROBLEM DESCRIPTION: Mismatched TIMESTAMP precision causes   *
        *                      range and BETWEEN predicates to not use *
        *                      page range screening.                   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        This fix improves the evaluation of range and BETWEEN predicates
        with mismatched TIMESTAMP precision so that page range screening
        may be applied.

        The predicates that are affected are:

        1, <TIMESTAMP column>    <    <host-var or string 
constant>
 
        2, <TIMESTAMP column>    <=   <host-var or string 
constant>
 
        3, <TIMESTAMP column>    >    <host-var or string 
constant>
 
        4, <TIMESTAMP column>    >=   <host-var or string 
constant>
 
        5, <TIMESTAMP column> BETWEEN <host-var or string constant>
                                  AND <host-var or string constant>

        DB2 code has been modified to support this.

        The change adds an online-changeable subsystem parameter in
        DSN6SPRM called PGRNGSCR that specifies whether to enable
        page range pruning in order to improve performance of queries
        that contain one or more of the following predicates:
          <TIMESTAMP column>    <    <host-var or string 
constant>
 
          <TIMESTAMP column>    <=   <host-var or string 
constant>
 
          <TIMESTAMP column>    >    <host-var or string 
constant>
 
          <TIMESTAMP column>    >=   <host-var or string 
constant>
 
          <TIMESTAMP column> BETWEEN <host-var or string constant>
                                 AND <host-var or string constant>
1       Valid settings are:
        - NO : Do not enable this optimizer change.
               ==> This is the default setting
        - YES: Enable the change.  Do not use this setting
               unless advised to do so by IBM service.

        Special attention for data sharing customers:
         * Do not specify PGRNGSCR=YES on any member of the group until
           the fixing PTF for this APAR has been applied to all members.
           Otherwise, DB2 can experience abend 04E-00E70005 at
           DSNXRTIM:P017
         * If you specify PGRNGSCR=YES on any member, it is recommended
           that you specify it on all members.  Not specifying the same
           option on all members may result in member flip-flop
           behavior.

        Additional keywords: SQLTIMESTAMP SQLACCESSPATH SQLPERFORMANCE
                             PAGERANGE SQLBETWEEN SQLLT SQLGT ABEND04E
                             RC00E70005 DSNXRTIM P017
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM81692
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM75486:

        See PM75486 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM75486 corrects a problem that incorrect output could happen
        for an SQL statement that satisfies all of the following
        conditions:

        1. It contains a table expression or view with a set operator,
           and the table expression or view is materialized.
        2. It contains a LIKE predicate that can be pushed down to the
           materialized table expression or view.
        3. After push down, the LIKE predicate contains an expression,
           which matches to an index on expression.
        4. The expressions in the different set branches return data
           with different nullability.

        To make this fix effective for a static application, it must 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 PM70345:

        See PM70345 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM70345 corrects a problem that performance regression could
        happen for a static SQL statement that has a non-boolean term
        predicate with Timestamp column.
1
        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM53364:

        See PM53364 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM53364 corrects a problem that
         An incorrout may occur when the query satisfies all of below
         conditions:

         1,A String representation of timestamp value is used as one
           parameter of a scalar function.

         2,Above scalar function is referenced in the user query's
           predicate.

         3,The result of the scalar function is used to compare with
           another timestamp value.

        To make this fix effective for a static application, it must 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 PM47894:

        See PM47894 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM47894 corrects a problem that
        an incorrout may occur when user's SQL statement satisfies all
        of following conditions:

        1, The SQL statement contains a BETWEEN predicate which
           references a CASE expression in its low or high operator.

        2, The CASE expression references a scalar fullselect in its
           searched-when clause.


        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      ACTION:
        ***Actions for APAR PM81692 (V10)
        This PTF adds an online-changeable subsystem parameter in
        DSN6SPRM called PGRNGSCR that specifies whether to enable
        page range pruning in order to improve performance of queries
        that contain one or more of the following predicates:
          <TIMESTAMP column>    <    <host-var or string 
constant>
 
1         <TIMESTAMP column>    <=   <host-var or string 
constant>
 
          <TIMESTAMP column>    >    <host-var or string 
constant>
 
          <TIMESTAMP column>    >=   <host-var or string 
constant>
 
          <TIMESTAMP column> BETWEEN <host-var or string constant>
                                 AND <host-var or string constant>
        Valid settings are:
        - NO : Do not enable this optimizer change.
               ==> This is the default setting
        - YES: Enable the change.  Do not use this setting
               unless advised to do so by IBM service.

        Special attention for data sharing customers:
         * Do not specify PGRNGSCR=YES on any member of the group until
           this PTF has been applied to all members.  Otherwise, DB2 can
           experience abend 04E-00E70005 at DSNXRTIM:P017
         * If you specify PGRNGSCR=YES on any member, it is recommended
           that you specify it on all members.  Not specifying the same
           option on all members may result in member flip-flop
           behavior.

        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) Rebind any applications using one or more of the
            aforementioned predicates.

        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 PGRNGSCR=<x>, where <x> is
              NO or YES, to the invocation of the DSN6SPRM
              macro.  Make sure to add a continuation character in
              column 72 if needed.  If you omit adding PGRNGSCR here,
              the value will be set to the default of NO when you
              assemble the DSNZPxxx module.

1             Special attention for data sharing customers:
              - Do not specify PGRNGSCR=YES on any member of the group
                until this PTF has been applied to all members.
                Otherwise, DB2 can experience abend 04E-00E70005 at
                DSNXRTIM:P017
              - If you specify PGRNGSCR=YES on any member, it is
                recommended  that you specify it on all members. Not
                specifying the same option on all members may result
                in member flip-flop behavior.

            * 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 PGRNGSCR to the CLIST default
             input members, DSNTIDXA and DSNTIDXB, in the SDSNSAMP
             target library. You need to add these entries to all
             private copies of your CLIST output DSNTIDxx member.  In
             each such copy, add the following lines:

        PGRNGSCR CHAR  M  NO          YES           <x>

             Change <x> to the value you specified for PGRNGSCR in
             step (2), above.

        ----------------------------------------------------------------
        (4) Rebind any applications using one or more of the
            aforementioned predicates.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.

        End of actions for APAR PM81692 (V10)
      ACTION:
        ***Action for PM79804 (V10)

        This PTF modifies the DB2 installation CLIST to correct errors
        in the migration handling of the DSN6SPRM.LRDRTHLD parameter.

        Actions for current DB2 10 customers:
        ------------------------------------
        This PTF modifies CLIST member DSNTINST only in the
        prefix.SDSNCLST target library.  After applying the PTF, you
        need to redo any record format changes and reapply any tailoring
        you have done to your copies of this CLIST.  You may also want
        to move it to the prefix.NEW.SDSNCLST data set, where the CLISTs
        processed by job DSNTIJVC reside.
    COMMENTS:
1     CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSN@XAZP  PM81692
       DSNDQWPZ  PM81692
       DSNDSPRM  PM81692
       DSNTIDXA  PM81692
       DSNTIDXB  PM81692
       DSNTIJUZ  PM81692
       DSNTINST  PM81692
       DSNTXAZP  PM81692
       DSNWZIFA  PM81692
       DSNXGSFN  PM81692
       DSNXOEXF  PM81692
       DSNXOMPS  PM81692
       DSNXOSCD  PM81692
       DSNXOW2C  PM81692
       DSNXOW2D  PM81692
       DSNXRTIM  PM81692
       DSN6SPRM  PM81692

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM81692   DSN@XAZP DSNDQWPZ DSNDSPRM DSNTIDXA DSNTIDXB DSNTIJUZ
                 DSNTINST DSNTXAZP DSNWZIFA DSNXGSFN DSNXOEXF DSNXOMPS
                 DSNXOSCD DSNXOW2C DSNXOW2D DSNXRTIM DSN6SPRM

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNTXAZP
       DSNWZIFA
       DSNXGSFN
       DSNXOEXF
       DSNXOMPS
       DSNXOSCD
       DSNXOW2C
       DSNXOW2D
       DSNXRTIM

      MACROS
       DSN@XAZP
       DSNDQWPZ
       DSNDSPRM
       DSNTIDXA
       DSNTIDXB
       DSNTIJUZ
       DSNTINST
       DSN6SPRM

      LISTEND
 UK93300 COVER LETTER END


 UK93369 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM76288 -
        ****************************************************************
        * USERS AFFECTED: All IRLM220(HIR2220) and IRLM230(HIR2230)    *
1       *                 users data sharing SYSPLEXDS.                *
        ****************************************************************
        * PROBLEM DESCRIPTION: After IRLM termination via ABEND        *
        *                      command  F irlmproc,ABEND,              *
        *                      IMS XRF takeover process is delayed     *
        *                      for 3 seconds as IRLM hasn't driven     *
        *                      Status Exit in IMS. IMS may see         *
        *                      additional lock failures during the     *
        *                      3 seconds delay time                    *
        ****************************************************************
        * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
        ****************************************************************
        IRLM ESTAE in DXRRL070 waits for 3 secs before proceeding if it
        needs to Disconnect from the data sharing group. This delay in
        calling the Status Exit in IMS may result in IMS continuing to
        issue requests to IRLM. These requests are rejected by IRLM.
        XRF takeover processing is delayed until IRLM drives the Status
        Exit.
        GEN:
        KEYWORDS:

        *** END IMS KEYWORDS ***
        This APAR changes IRLM ESTAE logic to be able to issue Status
        Exit drive to DBMS, sooner. If IRLM needs to Disconnect from the
        data sharing group, IRLM will POST an ECB to ESTAE code as soon
        as the Disconnect is done. IRLM will also unhook from SSI, early
        to prevent requests being issued to its associated DBMS.
    COMPONENT:  5695-16401-HIR2230
    APARS FIXED: PM76288
    SPECIAL CONDITIONS:
      COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DXRRL070  PM76288
       DXRRL711  PM76288

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM76288   DXRRL070 DXRRL711

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DXRRL070
       DXRRL711

      LISTEND
 UK93369 COVER LETTER END


 UK93392 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM83457 -
        ****************************************************************
        * USERS AFFECTED: DB2 10 for z/OS users joining 3 or more      *
        *                 tables in a query block.                     *
1       ****************************************************************
        * PROBLEM DESCRIPTION: DB2 may select an inefficient join      *
        *                      sequence for a query if the query has   *
        *                      a query block with a join of 3 or       *
        *                      more tables.                            *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        DB2 may select an inefficient join sequence for a query if the
        query has a query block with a join of 3 or more tables. In
        particular, when there are multiple tables joined, the tables
        joined via indexes may be joined at a later position in the
        inefficient access path while joining them earlier may provide
        better performance.

        Additional Keywords:
        SQLACCESSPATH SQLPERFORMANCE
        Code has been modified to correct the problem described as
        above.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM83457
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM83457:

        A rebind is necessary for static applications to rebuild
        access paths based on the changes in this APAR.

        PM83457 corrects a problem that the DB2 optimizer may select an
        inefficient join sequence for a query if the query has a query
        block with a join of 3 or more tables.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM73214:

        A rebind is necessary for static applications to rebuild
        access paths based on the changes in this APAR.

        PM73214 corrects a problem of inaccurate cost estimation for
        a query when the query contains a view or table expression with
        UNION ALL.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM72676:

        A rebind is necessary for static applications to rebuild
1       access paths based on the changes in this APAR.

        PM72676 corrects a problem of inaccurate cost estimation for
        a query when the query contains nested non-correlated
        subqueries.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM58932:

        A rebind is necessary for static applications to rebuild
        access paths based on the changes in this APAR.

        PM58932 corrects a problem that DB2 may choose an inefficient
        join sequence for a query joining 3 or more tables.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM34814:

        See PM34814 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM34814 corrects a problem that DB2 may select an inefficient
        join sequence for a query if a declared global temporary table
        is involved or statistics on join columns are not collected.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOPKN  PM83457
       DSNXOTS   PM83457

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM83457   DSNXOPKN DSNXOTS

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOPKN
       DSNXOTS

      LISTEND
 UK93392 COVER LETTER END


 UK93422 COVER LETTER START
1   PROBLEM DESCRIPTION(S):
      PM81748 -
        ****************************************************************
        * USERS AFFECTED: DB2 V10 users.                               *
        ****************************************************************
        * PROBLEM DESCRIPTION: In a data sharing environment, ABEND0C6 *
        *                      in IXLM2VSR or resource unavailable     *
        *                      reason code RC00C20222 for an index     *
        *                      root page.                              *
        *                                                              *
        *                      Failure to time out on a page latch     *
        *                      resulting in indefinite suspends in     *
        *                      DSNB1TMR.                               *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        In data sharing, when performing a "fast path" get-page on an
        index root page, DB2 may issue a test-page operation even though
        the index is in GRECP state.  In most cases this simply causes
        the get-page operation to fail with RNA RC00C20222 instead of
        the more appropriate RC00C20206.  However, it may also result
        in an ABEND0C6 in IXLM2VSR.

        The page latch timeout function is not effective in V10, which
        can cause an application to wait indefinitely in DSNB1TMR for a
        page latch if the latch is never freed.  Note that the timeout
        interval for a page latch is usually 10 minutes, and a timeout
        will not normally happen except due to a DB2 code error.
        The fast-path get-page logic has been modified to check the
        index for GRECP status before issuing a test-page, rather than
        doing it afterward.

        The page latch logic has been modified to ensure that the
        timeout function works correctly.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM81748
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNB1GFP  PM81748
       DSNB1ULT  PM81748

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM81748   DSNB1GFP DSNB1ULT

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNB1GFP
       DSNB1ULT

      LISTEND
 UK93422 COVER LETTER END

1
 UK93436 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM74659 -
        ****************************************************************
        * USERS AFFECTED: ALL DB2 for z/OS V10 users                   *
        ****************************************************************
        * PROBLEM DESCRIPTION: The DB2 directory data base (DSNDB01)   *
        *                      could experience significant space      *
        *                      growth resulting from BIND/REBIND       *
        *                      operations, DDL or Utility activity     *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The BIND/REBIND operation involves the need to delete the
        existing old package and reinsert the new package in the
        SPT01 table space.
        The deleted space within the same UR that is performing a
        REBIND operation can not be reused until the UR is committed.
        In addition, the subsequent insert of the new package may
        not reuse the committed delete space promptly due to the
        clustering order of the record within the table space.
        As a result, the SPT01 table space could experience
        significant space growth resulting from a large volume of
        concurrent BIND/REBIND operations.
        DB2 has been modified to allow a UR to reuse its own deleted
        space within the same commit scope if it has exclusive control
        of the page. In additional, the search algorithm has also been
        changed to reuse the deleted space sooner. These changes only
        apply to the DB2 directory data base (DSNDB01).
      PM81485 -
        ****************************************************************
        * USERS AFFECTED: ALL DB2 for z/OS V10 users                   *
        ****************************************************************
        * PROBLEM DESCRIPTION: The DB2 directory data base (DSNDB01)   *
        *                      could experience significant space      *
        *                      growth resulting from BIND/REBIND       *
        *                      operations, DDL or Utility activity.    *
        ****************************************************************
        * RECOMMENDATION:                                              *
        *                                                              *
        *                                                              *
        *                                                              *
        *                                                              *
        *                                                              *
        *                                                              *
        *                                                              *
        *                                                              *
        *                                                              *
        *                                                              *
        *                                                              *
        *                                                              *
        *                                                              *
        *                                                              *
        *                                                              *
        *                                                              *
1       *                                                              *
        *                                                              *
        ****************************************************************
        The BIND/REBIND operation involves the need to delete the
        existing old package and reinsert the new package in the
        SPT01 table space.
        The deleted space within the same UR that is performing a
        REBIND operation can not be reused until the UR is committed.
        In addition, the subsequent insert of the new package may
        not reuse the committed delete space promptly due to the
        clustering order of the record within the table space.
        As a result, the SPT01 table space could experience
        significant space growth resulting from a large volume of
        concurrent BIND/REBIND operations.








        DB2 has been modified to allow a UR to reuse its own deleted
        space within the same commit scope if it has exclusive control
        of the page. In additional, the search algorithm has also been
        changed to reuse the deleted space sooner. In any case if the
        UR doing BIND/REBIND process needs to roll back, the log
        apply phase will process the log record by redoing the
        change physically instead of pseudo delete process.
        These changes only apply to the UTS table space created
        in the DB2 directory data base (DSNDB01).
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM74659,PM81485
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNIBHUN  PM74659  PM81485
       DSNIREPR  PM74659  PM81485
       DSNISGRT  PM74659  PM81485
       DSNISGSC  PM74659  PM81485
       DSNISUPI  PM74659  PM81485
       DSNKPOSI  PM74659  PM81485

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM74659   DSNIBHUN DSNIREPR DSNISGRT DSNISGSC DSNISUPI DSNKPOSI
       PM81485   DSNIBHUN DSNIREPR DSNISGRT DSNISGSC DSNISUPI DSNKPOSI

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIBHUN
       DSNIREPR
       DSNISGRT
       DSNISGSC
1      DSNISUPI
       DSNKPOSI

      LISTEND
 UK93436 COVER LETTER END


 UK93442 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM82787 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS V8, DB2 V9 and V10 for z/OS *
        *                 users of an SQL statement that converting a  *
        *                 FLOAT value to a DECIMAL value.              *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C4 RC00000011 at the location     *
        *                      DSNXGRDS DSNXOLTN OFFSET0342 could      *
        *                      happen for an SQL statement that        *
        *                      converting a FLOAT value to a DECIMAL   *
        *                      value.                                  *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An example is shown below:

        CREATE TABLE T1 (
          C1 DECIMAL
        );

        INSERT INTO T1 VALUES(1.23E3);

        DB2 did not correctly process the aforementioned SQL statements,
        which caused the ABEND.
        DB2 has been modified to correctly process the aforementioned
        SQL statement, so there will be no ABEND.

        Additional keywords:
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM82787
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOLTN  PM82787

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM82787   DSNXOLTN

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOLTN

      LISTEND
 UK93442 COVER LETTER END
1

 UK93469 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM76946 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of RECOVER         *
        *                 utility with the BACKOUT YES option.         *
        ****************************************************************
        * PROBLEM DESCRIPTION: RECOVER utility with the BACKOUT YES    *
        *                      option does extraneous opens and        *
        *                      closes of the target objects which      *
        *                      can cause longer elapsed times and      *
        *                      increased CPU usage.                    *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The RECOVER utility with the BACKOUT YES option invokes
        opens and closes of the target objects unnecessarily
        which may result in longer elapsed times and increased
        CPU usage.
        The RECOVER utility has been modified to eliminate the
        unnecessary close and open of the target objects.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM76946
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNIUNDO  PM76946
       DSNUCAIN  PM76946
       DSNUCALA  PM76946
       DSNUCALU  PM76946

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM76946   DSNIUNDO DSNUCAIN DSNUCALA DSNUCALU

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIUNDO
       DSNUCAIN
       DSNUCALA
       DSNUCALU

      LISTEND
 UK93469 COVER LETTER END


 UK93476 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM82943 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 9 and 10 for z/OS.          *
        ****************************************************************
1       * PROBLEM DESCRIPTION: DB2 threads can hang on a latch as      *
        *                      a result of recovery for an             *
        *                      ABEND04E RC00E20016 IN CSECT DSNVXUL0.  *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Recovery actions from an ABEND04E RC00E20016 in CSECT
        DSNVXUL0 can incorrectly reset internal tracking bits that
        determine if there are suspended agents waiting on a latch.

        This can lead to the suspended agents never resuming and
        suffering a hang.
        CSECT DSNVLFRR has been modified to correctly determine
        the status of latch waiters before dump and recovery actions
        are initiated, allowing agents to be resumed successfully.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM82943
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNVLFRR  PM82943

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM82943   DSNVLFRR

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNVLFRR

      LISTEND
 UK93476 COVER LETTER END


 UK93481 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM80664 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 9 for z/OS or DB2 10 for    *
        *                 z/OS who use DSNREXX.                        *
        ****************************************************************
        * PROBLEM DESCRIPTION: When DSNREXX processes a FETCH          *
        *                      statement with LOB columns, the         *
        *                      following may occur:                    *
        *                      + ABEND04E RC00E20003                   *
        *                      + ABEND878 RC00000010                   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When DSNREXX processes a FETCH statement with one or more LOB
        columns, it obtains storage.  This storage may not always be
        released and a subsequent request for storage may fail with one
        of the following:

1         ABEND04E RC00E20003
          ABEND878 RC00000010
        DSNREXX is modified to release storage.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM80664
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNTZFET  PM80664

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM80664   DSNTZFET

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNTZFET

      LISTEND
 UK93481 COVER LETTER END


 UK93488 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM78005 -
        ****************************************************************
        * USERS AFFECTED: All IRLM220 (HIR2230) and IRLM230 (HIR2230)  *
        *                 users.                                       *
        ****************************************************************
        * PROBLEM DESCRIPTION: IRLM enhancement to handle large number *
        *                      of waiters in IRLM.                     *
        ****************************************************************
        * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
        ****************************************************************
        IRLM processing of lock resource waiters for timeout slows
        down when there are large number of waiters in a data sharing
        group. This results in lock waiting more than the timeout value
        specified in IRLMRWT.
        This APAR improves timeout processing in IRLM. IRLM will use
        lock storage from RLB subpool instead of obtaining it for every
        waiter from private storage during timeout and deadlock process.
        Number of waiters that can be timed out per cycle has been
        increased from 25 to 50. This should reduce the waiter backlog
        faster but if the number of waiters on a single member is
        higher than 50 during a given cycle, some may still experience
        timeout values higher than specified.
    COMPONENT:  5695-16401-HIR2230
    APARS FIXED: PM78005
    SPECIAL CONDITIONS:
      COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DXRRL24B  PM78005
1      DXRRL24F  PM78005
       DXRRL246  PM78005
       DXRRL247  PM78005
       DXRRL248  PM78005

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM78005   DXRRL24B DXRRL24F DXRRL246 DXRRL247 DXRRL248

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DXRRL24B
       DXRRL24F
       DXRRL246
       DXRRL247
       DXRRL248

      LISTEND
 UK93488 COVER LETTER END


 UK93532 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM77111 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for zOS users                        *
        ****************************************************************
        * PROBLEM DESCRIPTION: Collecting documentation for problems   *
        *                      associated with RID POOL exhausting     *
        *                      available storage is very difficult. A  *
        *                      easy, non-disruptive solution is        *
        *                      needed.                                 *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When DB2 encounters problems due to exhausted available storage
        in the RID Pool, it is very difficult to collect the
        documentation needed to analyze the cause. By the time a console
        dump can be taken, the needed data may not be in memory.  A real
        time solution is needed to address this.
        A new serviceability IFCID0375 is introduced. If this IFCID is
        active and a RID Pool out of storage condition is encountered,
        a trace will be written.  DSN1SDMP job can be used to promptly
        take a dump of a system of analysis.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM77111
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNDQWHS  PM77111
       DSNDQW05  PM77111
       DSNIREFS  PM77111
       DSNIREPR  PM77111
       DSNIRIDL  PM77111
1      DSNIRIDR  PM77111
       DSNISRTI  PM77111
       DSNIXLDR  PM77111
       DSNURBXA  PM77111
       DSNWVINT  PM77111
       DSNXRRID  PM77111
       DSNXRRI9  PM77111
       DSNXSFIN  PM77111
       DSNXSFML  PM77111
       DSNXSFPR  PM77111
       DSNXSFUN  PM77111
       DSNXSMIN  PM77111
       DSNXSMRL  PM77111
       DSNXSMUN  PM77111
       DSNXSPRM  PM77111

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM77111   DSNDQWHS DSNDQW05 DSNIREFS DSNIREPR DSNIRIDL DSNIRIDR
                 DSNISRTI DSNIXLDR DSNURBXA DSNWVINT DSNXRRID DSNXRRI9
                 DSNXSFIN DSNXSFML DSNXSFPR DSNXSFUN DSNXSMIN DSNXSMRL
                 DSNXSMUN DSNXSPRM

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIREFS
       DSNIREPR
       DSNIRIDL
       DSNIRIDR
       DSNISRTI
       DSNIXLDR
       DSNURBXA
       DSNWVINT
       DSNXRRID
       DSNXRRI9
       DSNXSFIN
       DSNXSFML
       DSNXSFPR
       DSNXSFUN
       DSNXSMIN
       DSNXSMRL
       DSNXSMUN
       DSNXSPRM

      MACROS
       DSNDQWHS
       DSNDQW05

      LISTEND
 UK93532 COVER LETTER END


 UK93554 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM80722 -
        ****************************************************************
1       * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS                *
        *                 users whose query running with sort          *
        *                 merge join method for outer join.            *
        ****************************************************************
        * PROBLEM DESCRIPTION: Performance problem when sort merge     *
        *                      join was chosen for outer join process  *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When DB2 is running in sort merge join method for a  left
        outer join query, the performance is not optimized.

        This performance problem is data dependent. Only when certain
        data patterns are observed in the tables of the join, we will
        have this problem.

        The problem is that inner table of the join will be scanned more
        than needed when search for match of each outer table row. So,
        when both inner table and outer table are very large, the query
        may not be finished in reasonable time.

        Here is a simple example of this problem.

         SELECT *
           FROM T1
             LEFT JOIN T2
           ON T1.C1 = T2.C2;

        When sort merge join is chosen to process the left outer join
        in this query, and the data fall into certain patterns, we will
        hit the performance issue.
        DB2 has been fixed to improve the performance of sort
        merge join for left outer join case, so that the
        query that could not be finished before can be finished
        now in reasonable time.


        Additional keywords: SQLOUTERJOIN SQLJOIN SQLOUTER
                             SQLPERFORMANCE
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM80722
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXROJL  PM80722
       DSNXROL9  PM80722

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM80722   DSNXROJL DSNXROL9

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXROJL
1      DSNXROL9

      LISTEND
 UK93554 COVER LETTER END


 UK93556 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM62042 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS data sharing users with     *
        *                 indexes.                                     *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNKFTCH            *
        *                      ERQUAL5004 occurred during index        *
        *                      access.                                 *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        ABEND04E RC00C90101 DSNKFTCH ERQUAL5004 occurred during index
        access due to an index page regression.  The index page
        regression was introduced by a timing window during a Group
        Buffer pool page access where an update to an index page went
        undetected.
        Code has been modified to do additional page update detection
        during Group Buffer pool page access.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM62042
    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  PM62042
       DSNKDLE   PM62042
       DSNKINSL  PM62042

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM62042   DSNB1SWS DSNKDLE  DSNKINSL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNB1SWS
       DSNKDLE
       DSNKINSL

      LISTEND
 UK93556 COVER LETTER END


 UK93558 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM81673 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of                 *
1       *                 DSN1COPY utility                             *
        ****************************************************************
        * PROBLEM DESCRIPTION: DSN1COPY issues                         *
        *                          DSN1961I - PIECE NUMBER xxxx IS     *
        *                                     INVALID                  *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        DSN1COPY needs the data set size to process the input data set.
        In some cases, the data set size used was not the expected
        value. This caused DSN1COPY processing to be halted and the
        following message was issued:

          DSN1961I - PIECE NUMBER xxxx IS INVALID

        The cause of the unexpected data set size was one of the
        following:

        (1) The DSSIZE parameter was specified by the user but was not
        honored for non-partitioned table spaces and universal table
        spaces (UTS).

        (2) The LARGE parameter is associated with a data set size of
        4G, but when LARGE was specified by the user, it was not honored
        for non-partitioned table spaces and universal table spaces
        (UTS).

        (3) When neither the DSSIZE nor LARGE parameters are specified,
        DSN1COPY should obtain the data set size from the header
        page, if it is available.  This was not happening for a non-UTS.
        DSN1COPY is modified to pick up the DSSIZE value from:
         (1) the DSSIZE parameter or the LARGE parameter, if specified
         (2) the header page value, if available
         (3) the default value
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM81673
    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  PM81673
       DSN1SDEF  PM81673

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM81673   DSN1COPY DSN1SDEF

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSN1COPY
       DSN1SDEF

      LISTEND
 UK93558 COVER LETTER END

1
 UK93559 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM80156 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of data sharing.   *
        ****************************************************************
        * PROBLEM DESCRIPTION: IRLM ABEND MODULE DXRRL2R2:03 PM00614   *
        *                      RETLOCK DETECTED INCOMPATIBLE LOCK      *
        *                      during GROUP RESTART                    *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available.         *
        ****************************************************************
        During group restart, IRLM detected an incompatible lock and
        abended because two data sharing members requested the same
        retained utility ID (UID) lock.

        The problem happened because DB2 failed to locate the UID UNLOCK
        log record for the matching UID LOCK log record, which resulted
        in unnecessary requests of retained UID locks.
        DB2 has been modified to correctly detect matching UID LOCK and
        UNLOCK log records and avoid unnecessary requests of retained
        UID locks.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM80156
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUGCUR  PM80156

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM80156   DSNUGCUR

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUGCUR

      LISTEND
 UK93559 COVER LETTER END


 UK93596 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM84463 -
        ****************************************************************
        * USERS AFFECTED: DB2 10 for z/OS users of RENAME TABLE.       *
        ****************************************************************
        * PROBLEM DESCRIPTION: SYSIBM.SYSTABAUTH field, STNAME, is     *
        *                      not updated to reflect the new name     *
        *                      after RENAME TABLE.                     *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
1       RENAME TABLE may fail to update STNAME in SYSIBM.SYSTABAUTH
        to reflect the new table name. The incorrect SYSTABAUTH.STNAME
        should not affect DB2 functionality.
        RENAME TABLE has been fixed to update STNAME to reflect the
        new table name.

        This apar will not fix existing STNAME fields.

        ADDITIONAL KEYWORDS:
        SQLRENAME
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM84463
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXIRTB  PM84463

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM84463   DSNXIRTB

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXIRTB

      LISTEND
 UK93596 COVER LETTER END


 UK93614 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM82708 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users.         *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNIDM.DSNIUNCA     *
        *                      ERQUAL5006 occurred when running REORG  *
        *                      utility with DIAGNOSE TYPE(677).        *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When running REORG utility with DIAGNOSE TYPE(677), index
        manager code is called to write diagnostic log records during
        REORG BUILD phase. An internal error was encountered by REORG
        utility and the diagnostic log records were processed by the
        cleanup routine, caused ABEND04E RC00C90101
        DSNIDM.DSNIUNCA ERQUAL5006.
        The diagnostic log records written during REORG utility
        should not be processed by DB2 log apply routines.
        Index manager code has been modified to write the diagnostic log
        records properly during REORG BUILD phase so these log records
        won't be processed by the cleanup routine.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM82708
1   SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNKFRMT  PM82708

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM82708   DSNKFRMT

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNKFRMT

      LISTEND
 UK93614 COVER LETTER END


 UK93629 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM75571 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 10 for z/OS Optimization    *
        *                 Hints.                                       *
        ****************************************************************
        * PROBLEM DESCRIPTION: Optimization Hints could receive        *
        *                      SQL code +395 with reason code '48' or  *
        *                      other various reason codes even if      *
        *                      the hint matches the access path chosen *
        *                      by DB2 when no hint is used.            *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Optimization hints could receive SQL code +395 with
        reason code '48' or various other reason codes even if
        the access path chosen by DB2 when no hints are applied is
        the same as the hint.  Optimization hints from DB2 V7 or older
        may have a different query block structure than newer releases
        of DB2.  Optimization hints that are read in will go through
        code that attempts to match the query blocks from the hint
        to the expected query block structure using DB2 10.  Two
        similar query blocks containing the same set of tables,
        the same number of child query blocks, and the same parent
        query blocks were mistakenly swapped in an attempt to
        match the hint, resulting in +395.

        Additional Keywords:
        OPTHINT OPTHINTS HINT SQLCODE395
        Code is changed to first compare query blocks directly
        one-to-one before swapping any query block numbers.  If
        the query block numbers and general structures match
        directly, then the hint is used without changing any
        query block numbers.  The function of this code is to
        attempt to use hints when they are provided even when
        there is some ambiguity as to which query blocks should
1       match up.  There is a small chance that this change
        could match the query blocks incorrectly since we cannot
        always determine definitively whether two query blocks are
        intended to match solely based on information available
        in the PLAN_TABLE.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM75571
    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  PM75571

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM75571   DSNXOPTJ

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOPTJ

      LISTEND
 UK93629 COVER LETTER END


 UK93641 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM81202 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 9 and 10 for z/OS.          *
        ****************************************************************
        * PROBLEM DESCRIPTION: 1. An ABEND0C4 may occur in CSECT       *
        *                      DSNVDTA with DB2 version 10 while       *
        *                      gathering information on suspended      *
        *                      threads when -DISPLAY THREAD command    *
        *                      is being processed.                     *
        *                                                              *
        *                      2. MSGDSNV404I incorrectly returns      *
        *                      '00'x instead of '40'x for inactive     *
        *                      threads.                                *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        1. Latch/Unlatch logic incorrectly sets the expected
        resumer information for suspended agents. This can lead to
        an ABEND0C4 in DISPLAY THREAD processing.

        2. DISPLAY THREAD returns '00'x instead of EBCDIC blank '40'x
        when returning information on inactive threads.
        1. Latch/Unlatch logic has been modified to set the expected
        resumer information correctly which allows CSECT DSNVDTA
        to process the value without suffering an ABEND0C4.

        2. Message DSNV404I has been modified to correctly return a
        '40'x character to indicate threads that are not active in DB2.
1   COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM81202
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNLDTI2  PM81202
       DSNVSLT0  PM81202
       DSNVXLT0  PM81202

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM81202   DSNLDTI2 DSNVSLT0 DSNVXLT0

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNLDTI2
       DSNVSLT0
       DSNVXLT0

      LISTEND
 UK93641 COVER LETTER END


 UK93644 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM84484 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 Utilities                   *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C4 PIC10 IEAVSTA0 AND ABEND04E    *
        *                      RC00E3000D DSNPCLO0 may occur when DB2  *
        *                      utility is processing data set rename.  *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        DB2 data set locate module is running in 31-bit addressing mode,
        but the caller in this case, a data set rename module, is not in
        31-bit when calling.  As a result ABEND0C4 IEAVSTA0 and ABEND04E
        RC00E3000D DSNPCLO0 may occur.
        DB2 data set rename module is switched to proper addressing mode
        before calling data set locate module.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM84484
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNPRNM0  PM84484

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM84484   DSNPRNM0

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1
      MODULES
       DSNPRNM0

      LISTEND
 UK93644 COVER LETTER END


 UK93648 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM84290 -
        ****************************************************************
        * USERS AFFECTED: DB2 9 for z/OS and DB2 10 for z/OS users     *
        *                 of ALTER INDEX on user-defined indexes       *
        *                 on catalog tables.                           *
        ****************************************************************
        * PROBLEM DESCRIPTION: ALTER INDEX may incorrectly result      *
        *                      in SQLCODE -607 when referencing a      *
        *                      user-defined index on a catalog table.  *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        ALTER INDEX may incorrectly result in SQLCODE -607 when a
        user-defined index on a catalog table has a SYSINDEXES.OBID
        value between  900-1699.
        DB2 has been modified to allow ALTER INDEX on user-defined
        indexes on catalog tables. ALTER INDEX will still result in
        SQLCODE -607 if the option is restricted.

        ADDITIONAL KEYWORDS:
        SQLCODE607
        SQLALTER
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM84290
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXIAIX  PM84290

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM84290   DSNXIAIX

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXIAIX

      LISTEND
 UK93648 COVER LETTER END


 UK93653 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM80983 -
1       ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of LOBs when       *
        *                 used in a LIKE predicate.                    *
        ****************************************************************
        * PROBLEM DESCRIPTION: An ABEND04E RC00C90101 at DSNOGETD 5007 *
        *                      can occur for a LOB column, defined in  *
        *                      a UNICODE table, is used in a LIKE      *
        *                      predicate when a 'resource unavailable' *
        *                      condition is detected.  Instead DB2     *
        *                      should issue SQLCODE -904 for 'resource *
        *                      unavailable' condition.                 *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An ABEND04E RC00C90101 can occur at location DSNOGETD 5007
        (ERQUAL5007) when processing a LOB column (in a UNICODE table)
        used in a LIKE predicate, a 'resource unavailable' condition is
        detected.  Instead DB2 should issue SQLCODE -904 for the
        'resource unavailable' condition.

        The following example illustrates the problem.

        1. Create a UNICODE Table with a LOB column and insert a row.

           CREATE TABLE T1
            (C1 CLOB(1K) , ID INT) CCSID UNICODE;

           INSERT INTO T1 VALUES(CLOB('ABCDE20'),1);


        2. Issue a SELECT statement which uses the LOB column C1
           in a LIKE predicate.

           SELECT * FROM T1 WHERE C1 LIKE '_E_';


        During the LIKE predicate processing for the LOB, if a 'resource
        unavailable' condition is detected at the same time (let's say
        on behalf of the SELECT job being canceled by the user), the LOB
        processing code does not handle the unexpected error condition
        correctly which leads to the aforementioned abend.

        Please note, other SQL errors during UNICODE LOB LIKE predicate
        processing can also trigger the above abend.
        The code in DB2 has been modified to prevent the abend for the
        stated conditions.  After this fix a correct SQLCODE will be
        issued instead of ABEND04E.

        Additional Keywords: DB2LOB SQLLOB SQLLIKE SQLCODE904
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM80983
    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      DSNOUL16  PM80983
       DSNOUL8   PM80983

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM80983   DSNOUL16 DSNOUL8

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNOUL16
       DSNOUL8

      LISTEND
 UK93653 COVER LETTER END


 UK93662 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM82111 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS       *
        *                 users of RECOVER utility on objects being    *
        *                 restored from a system level backup          *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00D10307 RC00C90070          *
        *                      MSGARC1801I MSGARC1860I MSGARC1802I     *
        *                      ARC1866 RC=32 on RECOVER utility        *
        *                      on an object which is restored          *
        *                      from a system level backup              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
          User ran RECOVER utility on a non-partitioned object whose
        recovery base was a system level backup (SLB).  During HSM
        processing of the data set the following messages were issued:
        ARC1801I FAST REPLICATION DATA SET RECOVERY IS
        ARC1801I (CONT.) STARTING FOR DATA SET
        ARC1801I (CONT.) aaaa.DSNDBC.bbbbbbb.cccccccc.I0001.A001,
        ARC1801I (CONT.) AT hh:mm:ss ON yyyy/mm/dd
        ARC1860I THE FOLLOWING 0001 DATA SET(S) FAILED DURING
        ARC1860I (CONT.) FAST REPLICATION DATA SET RECOVERY:
        ARC1860I (CONT.) aaaa.DSNDBC.bbbbbbb.cccccccc.I0001.A001,
        COPYPOOL=DSN$PZ$DB, DEVTYPE=TAPE, VOLUME=nnnnnn, ARC1866, RC=32
        ARC1802I FAST REPLICATION DATA SET RECOVERY HAS
        ARC1802I (CONT.) COMPLETED FOR DATA SET
        ARC1802I (CONT.) aaaa.DSNDBC.bbbbbbb.cccccccc.I0001.A001,
        ARC1802I (CONT.) AT hh:mm:ss ON yyyy/mm/dd, FUNCTION RC=0008,
        ARC1802I (CONT.) MAXIMUM DATA SET RC=0066
          This happened because the user specified that only SLBs on
        tape should be used for recovery (zparm
        RESTORE_RECOVER_FROMDUMP = Yes) but had made their SLB only
        on DASD.  This was unintentional but DB2 failed to detect it
        and the RECOVER job ultimately abended with
        ABEND04E RC00D10307 (log read failure due to invalid RBA values)
        and RC00C90070 (fast log apply failure due to internal error).
        These reason codes were not meaningful and in fact different
1       and unpredictable errors could have been seen.
          Code was changed in RECOVER utility to properly handle an
        error which is caused by the absence of an SLB on tape when
        the user specified zparm RESTORE_RECOVER_FROMDUMP = YES and
        the recovery is of an entire non-partitioned object.
          In this case
        msgDSNU1522I THE DFSMSHSM CALL TO RESTORE...FAILED WITH
                     RC = X'hsm-rc' AND REASON CODE X'hsm-rsc'...
        will now be issued and RC8 set for the object.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM82111
    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  PM82111
       DSNUCBRT  PM82111

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM82111   DSNUCBMT DSNUCBRT

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUCBMT
       DSNUCBRT

      LISTEND
 UK93662 COVER LETTER END


 UK93671 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM80345 -
        ****************************************************************
        * USERS AFFECTED: DB2 10 for z/OS users using IFCID 361.       *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C4 RC00000038 at DSNXVTRS+01D8    *
        *                      occurred during command processing      *
        *                      when IFCID 361 trace is started and     *
        *                      system parameter UIFCIDS is turned on.  *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        During DB2 command processing, when the system parameter,
        UIFCIDS is set to YES and IFCID 361 trace is turned on, an abend
         ABEND0C4 RC00000038 DSNXVTRS+01D8
        occurred while writing the trace record.

        The abend happened because an internal control structure needed
        for conversion is not available when DB2 tried to convert the
        command text to UNICODE.
        DB2 Code has been changed to fix the above abend during the
        command text conversion.

1       Additional keywords: OFFSET01D8 IFCID361 DSNXVTRS
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM80345
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXACKP  PM80345

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM80345   DSNXACKP

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXACKP

      LISTEND
 UK93671 COVER LETTER END


 UK93678 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM78224 -
        ****************************************************************
        * USERS AFFECTED: All DB2 Users preparing for new release      *
        ****************************************************************
        * PROBLEM DESCRIPTION: DB2 internal change to support future   *
        *                      functions.                              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        This APAR does not address or fix any problem in DB2. It
        contains changes in support of future function.
        This APAR does not have any external symptoms.
        The code logic is added to support a future new function.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM78224
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXELS1  PM78224

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM78224   DSNXELS1

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXELS1

      LISTEND
 UK93678 COVER LETTER END
1

 UK93682 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86224 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS users of Spatial support.   *
        ****************************************************************
        * PROBLEM DESCRIPTION: The prelink part DSN5SDEN includes      *
        *                      the wrong version of the objects        *
        *                      such as DSN5SK21 and DSN5SK40.          *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The function DB2GSE.IDXKEY2DG is failed with SQLCODE -430
        because the wrong entry (DSN5SK21) is loaded for this function.
        The problem is caused by the prelink during PTF process,
        therefor DSN5SDEN includes the wrong version of the object
        text files.
        The function DB2GSE.IDXKEY2DG is failed with SQLCODE -430
        because the wrong entry (DSN5SK21) is loaded instead of
        DSN5SK40. To fix the problem, the files and the prelink part
        are recompiled.
    COMPONENT:  5655-R1402-J2AG210
    APARS FIXED: PM86224
    SPECIAL CONDITIONS:
      COPYRIGHT: 5655-R1402 COPYRIGHT IBM CORP. 2006 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        For existing users, to be able to use the functions:
        DB2GSE.IDXKEY2DG, DB2GSE.GETGRIDMBR
        please submit the last two steps (CREATE02 and BINDSK19) of the
        DSN5SENB job.

        For new users, please follow the instructions contained in the
        publication "IBM Spatial Support for DB2 z/OS" to enable 
Spatial
 
        functionality.

        The warning message GIM43401W can be received when applying this
        apar. It can be ignored.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSN@SK19  PM86224
       DSN5SDEN  PM86224
       DSN5SENB  PM86224
       DSN5SK20  PM86224
       DSN5SK21  PM86224
       DSN5SK28  PM86224
       DSN5SK29  PM86224
       DSN5SK30  PM86224
       DSN5SK40  PM86224
       DSN5SK41  PM86224
       DSN5SK42  PM86224
       J2AG210J  PM86224

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1      PM86224   DSN@SK19 DSN5SDEN DSN5SENB DSN5SK20 DSN5SK21 DSN5SK28
                 DSN5SK29 DSN5SK30 DSN5SK40 DSN5SK41 DSN5SK42 J2AG210J

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSN5SDEN
       DSN5SK20
       DSN5SK21
       DSN5SK28
       DSN5SK29
       DSN5SK30
       DSN5SK40
       DSN5SK41
       DSN5SK42

      MACROS
       DSN@SK19
       DSN5SENB

      LISTEND
 UK93682 COVER LETTER END


 UK93705 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM84474 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of REORG AUX YES   *
        *                 on table space with inline LOB.              *
        ****************************************************************
        * PROBLEM DESCRIPTION: A REORG AUX YES on a table space with   *
        *                      an inline LOB column abended with       *
        *                      ABEND04E RC00E40005 and RC00E40347,     *
        *                      along with MSGICE083A because of space  *
        *                      unavailable for sort work data sets.    *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available.         *
        ****************************************************************
        A REORG with AUX YES ran on a base table space which contained
        a table with an inline LOB column.  REORG overestimated the
        average row length resulting in an ABEND04E RC00E40005 and
        RC00E40347, along with message ICE083A D RESOURCES WERE
        UNAVAILABLE FOR DYNAMIC ALLOCATION OF WORK DATA SETS (970C).
        This problem happened because the INLINE LOB length was
        calculated into the fixed column length.  If UTSORTAL=YES is
        used this can result in MSGDSNU3341I - CANNOT ALLOCATE SORT
        DATA SETS WITHIN 255 LIMIT.
        REORG code has been modified to calculate the INLINE LOB length
        into the variable column length.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM84474
    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
       DSNURFTB  PM84474

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM84474   DSNURFTB

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNURFTB

      LISTEND
 UK93705 COVER LETTER END


 UK93709 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM83959 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of REPAIR utility  *
        ****************************************************************
        * PROBLEM DESCRIPTION: Serviceability APAR for REPAIR SET      *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Serviceability APAR for REPAIR SET
        Serviceability APAR for REPAIR SET
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM83959
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNIDBMF  PM83959
       DSNUGDDN  PM83959

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM83959   DSNIDBMF DSNUGDDN

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIDBMF
       DSNUGDDN

      LISTEND
 UK93709 COVER LETTER END


 UK93711 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86956 -
        ****************************************************************
        * USERS AFFECTED: All data sharing users of DB2 for zOS.       *
        ****************************************************************
1       * PROBLEM DESCRIPTION: Data sharing member status remains QI   *
        *                      after the member has been shut down     *
        *                      with all Indoubt and Postponed-Abort    *
        *                      Units of Recovery (URs) completed. Also *
        *                      the Commit-LSN is not updated to show   *
        *                      that all URs are complete.              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        If there are Indoubt or Postponed-Abort URs during DB2 restart
        in data sharing mode, DB2 will set a 'QI' status flag.
        This will cause the member status in the -DISPLAY GROUP output
        to become 'QI' after the member is shut down even though
        all the Indoubt and Postponed-Abort URs have been completed.
        This also prevents DB2 shutdown from setting the Commit-LSN
        to all FF's, which can result in additional locking on the
        other members of the data sharing group.  The Commit-LSN
        for a DB2 member shutting down with all URs completed should
        be updated to all FF's in the SCA so that other members of
        the group can benefit from lock avoidance.
        DSNRIT02 has been changed to reset the QI status flag
        during DB2 shutdown when all URs are complete.  This will
        allow the Commit-LSN value to be updated correctly when
        DB2 shuts down in data sharing mode.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM86956
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNRIT02  PM86956

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM86956   DSNRIT02

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNRIT02

      LISTEND
 UK93711 COVER LETTER END


 UK93716 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM82999 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 Users                             *
        ****************************************************************
        * PROBLEM DESCRIPTION: With Zparm EVALUNC in effect,           *
        *                      when some applications query            *
        *                      non-UTS rows, uncommitted deleted       *
        *                      rows were skipped.  If those            *
        *                      uncommitted deleted rows were           *
1       *                      rolled back, the application            *
        *                      would not be able to return them        *
        *                      back to the user.                       *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        System zparm EVALUNC controls whether predicate
        evaluation is to be allowed on uncommitted data.
        When zparm EVALUNC was set to YES, Data that did
        not satisfy the predicate during evaluation but
        then, because of undo processing (ROLLBACK or
        statement failure), reverted to a state that did
        satisfy the predicate was missing from the answer
        set. Since EVALUNC is a system option, individual
        query statement is not able to turn it off.
        DB2 provides the ability to override ZPARM EVALUNC for
        individual remote statements via IBM Data Server Driver
        for ODBC and CLI.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM82999
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        See PK71143 APAR/PTF text in the PTF cover letter for
        additional information about why a REBIND is necessary.

        APAR PK71143 corrects a problem that can cause RS00C90096
        (number of page locks reached numlkus install limit) being
        issued for an update/delete/merge statement.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNIACCH  PM82999
       DSNIONX2  PM82999
       DSNIOST2  PM82999
       DSNIRNXT  PM82999
       DSNIRPRE  PM82999
       DSNISFRL  PM82999
       DSNISFS   PM82999
       DSNISRID  PM82999
       DSNKCKOP  PM82999
       DSNKFLST  PM82999
       DSNKFPRV  PM82999
       DSNKFTCH  PM82999
       DSNKINSL  PM82999
       DSNKNXT2  PM82999
       DSNLXPRS  PM82999
       DSNLXRSS  PM82999
       DSNXERT2  PM82999
       DSNXOMI   PM82999
       DSNXOMS   PM82999
1      DSNXOUID  PM82999

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM82999   DSNIACCH DSNIONX2 DSNIOST2 DSNIRNXT DSNIRPRE DSNISFRL
                 DSNISFS  DSNISRID DSNKCKOP DSNKFLST DSNKFPRV DSNKFTCH
                 DSNKINSL DSNKNXT2 DSNLXPRS DSNLXRSS DSNXERT2 DSNXOMI
                 DSNXOMS  DSNXOUID

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIACCH
       DSNIONX2
       DSNIOST2
       DSNIRNXT
       DSNIRPRE
       DSNISFRL
       DSNISFS
       DSNISRID
       DSNKCKOP
       DSNKFLST
       DSNKFPRV
       DSNKFTCH
       DSNKINSL
       DSNKNXT2
       DSNLXPRS
       DSNLXRSS
       DSNXERT2
       DSNXOMI
       DSNXOMS
       DSNXOUID

      LISTEND
 UK93716 COVER LETTER END


 UK93725 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM79556 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS       *
        *                 users of row change timestamp column.        *
        ****************************************************************
        * PROBLEM DESCRIPTION: UNLOAD FROMCOPY gets ABEND0C4           *
        *                      RC00000038 in DSNUULCA OFFSET55A2       *
        *                      when a row change timestamp column      *
        *                      was added to the table.                 *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        User ran an UNLOAD FROMCOPY on an image copy of a table space
        that had a table with an alter added row change timestamp
        column. The UNLOAD utility failed with ABEND0C4
        The cause is that DB2 referred to an internal control
        block that was not available.
        For the case when the internal control block is not available,
1       DB2 code has been modified to use other means to acquire a
        value to use to initialize the row change timestamp value when
        the column is missing from the row.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM79556
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNICOFS  PM79556
       DSNICUMW  PM79556
       DSNIDIFS  PM79556
       DSNIDLER  PM79556
       DSNIETRV  PM79556
       DSNIIDIS  PM79556
       DSNIKDEF  PM79556
       DSNILREP  PM79556
       DSNIMOFR  PM79556
       DSNIREFS  PM79556
       DSNIRELK  PM79556
       DSNIRFNX  PM79556
       DSNIRLPG  PM79556
       DSNISRTI  PM79556
       DSNITDLE  PM79556
       DSNIZMOS  PM79556
       DSNUULCA  PM79556

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM79556   DSNICOFS DSNICUMW DSNIDIFS DSNIDLER DSNIETRV DSNIIDIS
                 DSNIKDEF DSNILREP DSNIMOFR DSNIREFS DSNIRELK DSNIRFNX
                 DSNIRLPG DSNISRTI DSNITDLE DSNIZMOS DSNUULCA

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNICOFS
       DSNICUMW
       DSNIDIFS
       DSNIDLER
       DSNIETRV
       DSNIIDIS
       DSNIKDEF
       DSNILREP
       DSNIMOFR
       DSNIREFS
       DSNIRELK
       DSNIRFNX
       DSNIRLPG
       DSNISRTI
       DSNITDLE
       DSNIZMOS
       DSNUULCA

      LISTEND
 UK93725 COVER LETTER END
1

 UK93753 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM83778 -
        ****************************************************************
        * USERS AFFECTED: DB2 users of built-in stored procedure       *
        *                 SQLJ.ALTER_JAVA_PATH.                        *
        ****************************************************************
        * PROBLEM DESCRIPTION: When SQLJ.ALTER_JAVA_PATH is called     *
        *                      with a long PATH parameter, the call    *
        *                      will fail with the following error:     *
        *                                                              *
        *                      SQLCODE =-443                           *
        *                      SQLERRMC=ALTER_JAVA_PATH                *
        *                                 ALTER_JAVA_PATH              *
        *                                 M602 SQLCODE=-302 001        *
        *                      SQLERRP =DSNXRRTN                       *
        *                      SQLERRD =-818,0,0,-1,0,0                *
        *                      SQLWARN = , , , , , , , , , ,           *
        *                      SQLSTATE=00000                          *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The DB2 buffer that holds the SQL statement for
        ALTER_JAVA_PATH is not long enough so that the
        SQL statement will be truncated at execution time
        and results in SQL error -302.


        The size of DB2 buffer has been increased so that it can hold
        the SQL statement even when the PATH parameter reaches to the
        maximum 2048 characters.

        ADDITIONAL KEYWORDS:
        SQLSTOREDPROC
        ALTER_JAVA_PATH
        SQLCODE302
        SQLCODE443
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM83778
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        **Action for PM83778:

        Process the following command to bind the packages that
        updated as a result of installing this PTF:

        BIND PACKAGE(DSNJAR) MEMBER(DSNX9AJP) -
             ACTION(REPLACE) ISO(CS) CURRENTDATA(YES) ENCODING(EBCDIC) -
             LIBRARY('<prefix>.SDSNDBRM')

        Note: <prefix> is the data set prefix of your DB2 V9/V10
        target libraries
1   COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSN@9AJP  PM83778
       DSNX9AJP  PM83778

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM83778   DSN@9AJP DSNX9AJP

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNX9AJP

      MACROS
       DSN@9AJP

      LISTEND
 UK93753 COVER LETTER END


 UK93800 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM82954 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 (NFM) for z/OS users of LOAD      *
        *                 RESUME on compressed pageset or partition    *
        *                 (whose compression dictionary was generated  *
        *                 by insert), where at the time of LOAD RESUME *
        *                 the compression dictionary is at current end *
        *                 of data in the pageset or partition          *
        ****************************************************************
        * PROBLEM DESCRIPTION: MSGDSNI010I - BROKEN PAGE ACCESSED      *
        *                      TYPE00000302 MODNAME DSNILPG and        *
        *                      MSGDSNT500I - RESOURCE UNAVAILABLE      *
        *                      RC00C90087 issued during LOAD RESUME    *
        *                      on COMPRESS on INSERT table space       *
        *                      whose current end of data (highest page *
        *                      in pageset or partition) is a           *
        *                      dictionary page, corrupting this        *
        *                      dictionary page                         *
        *                                                              *
        *                      Then, potentially followed by           *
        *                      MSGDSNB209I - BUFFER MANAGER CLEANUP    *
        *                      ROUTINE (DSNB1CFC) HAS BEEN SCHEDULED   *
        *                      and MSGDSNB221I - BUFFER MANAGER        *
        *                      CLEANUP PROCESS WAS NOT REQUIRED        *
        *                                                              *
        *                      In addition to the dictionary page      *
        *                      being protected by broken page status,  *
        *                      the pageset or partition is left in     *
        *                      RECP status                             *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        During LOAD RESUME into a compressed table space whose
        compression dictionary was built during the INSERT process (new
1       in DB2 10 NFM) and dictionary pages are at the current end of
        data (meaning, page number HPGZ4PNO is the highest page in the
        pageset or partition), DB2 mistakenly attempted to load rows
        into the highest dictionary page, resulting in the symptoms
        mentioned above.

        In the affected code path, DB2 code did not account for the
        possibility that when a dictionary is built by the INSERT
        process, the dictionary pages need not be at the beginning of
        the pageset or partition. In this case, when looking for the
        current end of data for the LOAD to resume into, there were no
        pages after the dictionary pages and so DB2 mistakenly picked
        the final physical dictionary page as the resumption point.

        Given that this final physical dictionary page was being treated
        as a data page, the space search for a new row was relying on
        wrong information (scanning through a page "ID-map" which was
        not really an ID-map). As a result, the row was loaded into the
        dictionary page, corrupting the page's functional content.

        The aforementioned broken page-related messages were issued and
        the broken page status was turned on for protection, along with
        the RECP status on the pageset or partition.

        If this problem occurs, until the fix is available, the
        compression dictionary page shown in the message DSNI010I BROKEN
        PAGE ACCESSED should be recovered (e.g. from image copy),
        followed by REORG on the pageset or partition (regardless of
        whether KEEPDICTIONARY is specified or not). The REORG will
        move the compression dictionary pages to the beginning of the
        pageset/partition, in which case this problem does not exist.

        If this problem has not occurred and yet HPGZ4PNO happens to be
        the current end of data, until the fix is available, a REORG can
        be run on the pageset or partition (regardless of whether
        KEEPDICTIONARY is specified or not). The REORG will move the
        compression dictionary pages to the beginning of the pageset/
        partition, in which case this problem does not exist.
        Code has been changed for LOAD RESUME to tolerate compression
        dictionary pages being at current end of data.

        Additional keywords: SQLINSERT SQLMERGE
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM82954
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNIHLOD  PM82954
       DSNILPG   PM82954
       DSNIRLPG  PM82954
       DSNURWBF  PM82954

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM82954   DSNIHLOD DSNILPG  DSNIRLPG DSNURWBF
1
      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIHLOD
       DSNILPG
       DSNIRLPG
       DSNURWBF

      LISTEND
 UK93800 COVER LETTER END


 UK93810 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM81670 -
        ****************************************************************
        * USERS AFFECTED: DB2 10 for z/OS users who run a query on     *
        *                 the column DOWNERTYPE of the catalog table   *
        *                 SYSIBM.SYSPACKDEP and the owner of the       *
        *                 package is a role.                           *
        ****************************************************************
        * PROBLEM DESCRIPTION: SQLCODE -331 is returned when running   *
        *                      a query on the column DOWNERTYPE of     *
        *                      the catalog table SYSIBM.SYSPACKDEP     *
        *                      and the owner of the package is a       *
        *                      role. An example query is as follows.   *
        *                                                              *
        *                      SELECT DOWNERTYPE                       *
        *                      FROM SYSIBM.SYSPACKDEP                  *
        *                                                              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        SQLCODE -331 is returned when running a query on the column
        DOWNERTYPE of the catalog table SYSIBM.SYSPACKDEP and the
        owner of the package is a role. An example query is as follows.

        SELECT DOWNERTYPE
        FROM SYSIBM.SYSPACKDEP

        When binding a package whose owner is a role, DB2 did not set
        the value for column DOWNERTYPE of table SYSIBM.SYSPACKDEP
        correctly. An invalid value was inserted into the table for this
        column, and subsequent queries on the column will fail.
        Code has been modified to set the value of DOWNERTYPE correctly.
        This APAR does not fix the existing bad values in the catalog.
        See the HOLD text for the actions to fix the bad values.

        Additional keywords: SQLCODE331
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM81670
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
1       This APAR does not fix the existing bad values that are
        currently in the catalog. The following query can be used to
        see if there are any bad values in the catalog table.
        SELECT COUNT(*) FROM SYSIBM.SYSPACKDEP
        WHERE HEX(DOWNERTYPE) <> '20'
        AND HEX(DOWNERTYPE) <> '4C';
        If the result number is greater than zero, there are bad values
        in the table. To fix the bad values, the user can take one of
        the following actions.
        1. DROP/FREE the packages with the bad values and issue a new
           BIND PACKAGE command
        2. Contact DB2 for z/OS Service to get the CATMAINT job to fix
           the bad values
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNTBAB2  PM81670
       DSNTBRB2  PM81670

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM81670   DSNTBAB2 DSNTBRB2

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNTBAB2
       DSNTBRB2

      LISTEND
 UK93810 COVER LETTER END


 UK93840 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM83690 -
        ****************************************************************
        * USERS AFFECTED: All HIR2220 (IRLM220) and HIR2230 (IRLM230)  *
        *                 data sharing users SYSPLEXDS.                *
        ****************************************************************
        * PROBLEM DESCRIPTION: High CPU time and latch suspensions in  *
        *                      IRLM during COMMITs for packages using  *
        *                      RELEASE(DEALLOCATE) option for BIND.    *
        ****************************************************************
        * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
        ****************************************************************
        DB2 packages bound with RELEASE(DEALLOCATE) option don't release
        IRLM locks at the time of COMMIT. Over time, multiple threads
        may accumulate many locks with allocate duration causing IRLM
        lock chains per thread to grow. When these threads go through
        frequent updates and commits at the same time, IRLM could run
        into internal resource latch hash contention more often.  This
        occurs repeatedly because only locks matching the duration
        filter are being released during this Batch Unlock processing.
        Since IRLM is obtaining the resource latch before making the
        duration filter check, it results in high SRB time in IRLM
        as other threads get suspended on the held latch and are
        redriven after the latch is released during unlock.
1       GEN:
        KEYWORDS:
         SYSPLEXDS

        *** END IMS KEYWORDS ***
        This APAR provides an enhancement in Batch Unlock processing in
        IRLM when the unlock request is for all held locks.  Some
        validation checks, such as for duration, will be done prior
        to obtaining the resource latch during commit, improving
        overall unlock performance.
    COMPONENT:  5695-16401-HIR2230
    APARS FIXED: PM83690
    SPECIAL CONDITIONS:
      COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DXRRL130  PM83690

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM83690   DXRRL130

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DXRRL130

      LISTEND
 UK93840 COVER LETTER END


 UK93907 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM84134 -
        ****************************************************************
        * USERS AFFECTED: All DB2 V10 users using IRLM 2.3 (HIR2230).  *
        ****************************************************************
        * PROBLEM DESCRIPTION: Incorrect SQL Statement type is shown   *
        *                      in the  QW0172WY field of IFCID172 and  *
        *                      DSNT375I message.                       *
        ****************************************************************
        * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
        ****************************************************************
        IRLM passes a parameter list containing deadlock information to
        DB2 Deadlock Exit. The statement type information (dynamic or
        static)in the lock waiter or blocker information block, may not
        bet set correctly by IRLM. This may result in incorrect QW0172WY
        value reported in the IFCID172 record and the corresponding
        DSNT375I message.
        GEN:
        KEYWORDS:

        *** END IMS KEYWORDS ***
        IRLM will report SQL statement type correctly to DB2 Deadlock
        Exit when reporting a deadlock.
        DB2 APAR PM83838 will also be needed to correctly record SQL
1       statement type in IFCID 172.
    COMPONENT:  5695-16401-HIR2230
    APARS FIXED: PM84134
    SPECIAL CONDITIONS:
      COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DXRRL24C  PM84134
       DXRRL24I  PM84134

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM84134   DXRRL24C DXRRL24I

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DXRRL24C
       DXRRL24I

      LISTEND
 UK93907 COVER LETTER END


 UK93911 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM81676 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of Spatial         *
        *                 functions.                                   *
        ****************************************************************
        * PROBLEM DESCRIPTION: An intentional ABEND04E rc00E70005 can  *
        *                      occur at location DSNXRRP :M600 because *
        *                      the SQLCA does not match the DWA        *
        *                      (Diagnostic Work Area) when an error    *
        *                      is encountered. The problem came about  *
        *                      when executing a Spatial workload.      *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An intentional ABEND04E rc00E70005 can occur at location DSNXRRP
        M600 because the SQLCA does not match the DWA (Diagnostic Work
        Area) when an error is encountered.  The problem came about when
        executing a Spatial workload but can also occur otherwise.

        The failure occurs because DB2 is not properly restoring the
        SQLCA mode when it short-circuits the error processing.  The
        sequence is that DB2 saves the original SQLCA mode into a local
        flag but if another error on behalf of a Spatial UDF occurs,
        since DB2 does not restore the original SQLCA mode, the sanity
        check abend can occur.
        The code in DB2 has been modified to restore the SQLCA mode
        during error processing to avoid the intentional abend.

        Additional Keywords: SQLSPATIAL SQLUDF SQLGETDIAG

1   COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM81676
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXRRP   PM81676
       DSNXRRP9  PM81676

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM81676   DSNXRRP  DSNXRRP9

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXRRP
       DSNXRRP9

      LISTEND
 UK93911 COVER LETTER END


 UK93912 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM84810 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users with applications  *
        *                 that use SQL TRUNCATE Table statement and    *
        *                 bound with RELEASE(DEALLOCATE).              *
        ****************************************************************
        * PROBLEM DESCRIPTION: After TRUNCATE Table, DB2 keeps the     *
        *                      gross lock even after Commit if the     *
        *                      application is bound with               *
        *                      RELEASE(DEALLOCATE). This causes        *
        *                      other applications to be timed out      *
        *                      with RC00C9008E when trying to access   *
        *                      this table space.                       *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        DB2 will acquire a gross lock on the table space for Truncate
        table. If the application is bound with RELEASE(DEALLOCATE),
        then DB2 mistakenly keeps the gross lock across Commit and
        will not release it until this thread is deallocated.
        This causes other applications to be timed out when trying to
        access this table space with reason code 00C9008E.
        A fix is made in DB2 to release the gross lock on the table
        space at Commit. This will allow other applications to access
        this table space after Truncate table.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM84810
    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
       DSNICMT2  PM84810
       DSNILKDY  PM84810
       DSNIPSFI  PM84810
       DSNISDLE  PM84810
       DSNISEGD  PM84810

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM84810   DSNICMT2 DSNILKDY DSNIPSFI DSNISDLE DSNISEGD

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNICMT2
       DSNILKDY
       DSNIPSFI
       DSNISDLE
       DSNISEGD

      LISTEND
 UK93912 COVER LETTER END


 UK93918 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM83600 -
        ****************************************************************
        * USERS AFFECTED: All DB2 users of DELETE statement with AFTER *
        *                 DELETE Trigger and ALTER TABLE with ADD      *
        *                 COLUMN clause.                               *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C90D01 in DSNONLLE+19F8    *
        *                      on an INSERT statement.                 *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        After a base table is altered to add a new LOB column, if the
        table is defined with an AFTER-DELETE trigger, then DB2
        mistakenly handled the missing LOB column with a wrong default
        indicator value.
        DB2 code is fixed to handle the default value for the
        newly added LOB column under AFTER-DELETE trigger.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM83600
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNICUMW  PM83600
       DSNIDLER  PM83600
       DSNILREP  PM83600
       DSNIMOFR  PM83600
       DSNIRELK  PM83600
       DSNIRFNX  PM83600
       DSNITDLE  PM83600
1      DSNIZMOS  PM83600

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM83600   DSNICUMW DSNIDLER DSNILREP DSNIMOFR DSNIRELK DSNIRFNX
                 DSNITDLE DSNIZMOS

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNICUMW
       DSNIDLER
       DSNILREP
       DSNIMOFR
       DSNIRELK
       DSNIRFNX
       DSNITDLE
       DSNIZMOS

      LISTEND
 UK93918 COVER LETTER END


 UK93936 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86130 -
        ****************************************************************
        * USERS AFFECTED: All users of RESTORE SYSTEM Utility.         *
        ****************************************************************
        * PROBLEM DESCRIPTION: DSNP012I DSNPCNP0 - ERROR IN ICF        *
        *                      CATALOG FOR DB2 CATALOG AND             *
        *                      DIRECTORY OBJECTS DURING                *
        *                      RESTORE SYSTEM.                         *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        During the Restore System log apply phase, when opening the page
        set, incorrect VCAT name specified for catalog and directory
        object. Instead of using the VCAT name from Page set control
        (PSCR) log record, it uses the name from ACOM (ADMF
        communication Area). This results in Data Space Manager (DSM),
        unable to find the data set in ICF catalog. The correct logic is
        for restore system to always use VCAT name from the PSCR log
        record.
        Restore System log apply logic is modified so that it will
        always use VCAT name from the PSCR log record when opening
        the data set.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM86130
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNIRCSB  PM86130

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1      PM86130   DSNIRCSB

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIRCSB

      LISTEND
 UK93936 COVER LETTER END


 UK93941 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM79050 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users.                   *
        ****************************************************************
        * PROBLEM DESCRIPTION: Allied thread went to EOM               *
        *                      termination and received RC00E50005 in  *
        *                      DSNVXLT0.                               *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        1 - There was missing latch release prior to freeing the GMB
            blocks during allied EOM processing. In addition, the
            following two items were identified while researching
            the failure and fix.
        2 - DSNSRSUP super FRR return code,
            prevents down stream component FRR
            from being able to retry.  There were set based on what
            storage manager component was going to do in recovery,
            and were not expected to be used by down stream components.
        3 - DSNSCTL fails to set EBCML while scanning the local storage
            free chain which may result in CML not being released if
            a failure occurs, even though ebsmc was set to drive the
            storage manager recovery.
        1 - Code was added to release the GPVT latch prior to calling
            to free the GMB block.
        2 - The Storage Manager super FRR, was changed to set the
            return code passed back to the mainline FRR, to allow all
            down stream components to perform the recovery actions
            necessary.
        3 - The routine to determine the amount of free local storage
            in the address space, is changed to indicate when the CML
            lock is held and prevent the super FRR from doing retry
            should a failure occur.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM79050
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNSCTL   PM79050
       DSNSRSUP  PM79050
       DSNSTERM  PM79050
1
      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM79050   DSNSCTL  DSNSRSUP DSNSTERM

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNSCTL
       DSNSRSUP
       DSNSTERM

      LISTEND
 UK93941 COVER LETTER END


 UK93943 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM81681 -
        ****************************************************************
        * USERS AFFECTED: All DB2 z/OS users.                          *
        ****************************************************************
        * PROBLEM DESCRIPTION: An ABEND55F ABEND S055F occurred during *
        *                      DB2 start with ACCESS(MAINT).           *
        *                      The DB2 MSTR address space terminated   *
        *                      and DB2 failed to start.                *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An ABEND55F occurred during a DB2 startup with ACCESS(MAINT).
        -START DB2 PARM(module name) ACCESS(MAINT)
        Module DSNYASTR has been updated to prevent this ABEND55F.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM81681
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNYASTR  PM81681

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM81681   DSNYASTR

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNYASTR

      LISTEND
 UK93943 COVER LETTER END


 UK93953 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM78749 -
        ****************************************************************
1       * USERS AFFECTED: DB2 9 and 10 for z/OS users of CREATE        *
        *                 TABLESPACE                                   *
        ****************************************************************
        * PROBLEM DESCRIPTION: Default DSSIZE value is incorrect when  *
        *                      NUMPARTS is specified on CREATE         *
        *                      TABLESPACE                              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When CREATE TABLESPACE is specified with NUMPARTS between 16 and
        64 inclusive, and DSSIZE has not been specified, the DSSIZE is
        defaulted to an incorrect value of 4GB.
        DB2 has been fixed to set the default DSSIZE appropriately
        on CREATE TABLESPACE. This APAR does not fix existing DSSIZE
        values. In DB2 10 for z/OS, DSSIZE can be altered to the
        appropriate value via ALTER TABLESPACE.

        Additional Keywords:
        SQLCREATE
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM78749
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXICTS  PM78749

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM78749   DSNXICTS

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXICTS

      LISTEND
 UK93953 COVER LETTER END


 UK93957 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM82533 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 10 for z/OS who use table   *
        *                 expression, CTE or view with a correlated    *
        *                 IN subquery on the preserved side of OUTER   *
        *                 JOIN.                                        *
        ****************************************************************
        * PROBLEM DESCRIPTION: Performance may regress when an SQL     *
        *                      statement contains a table expression,  *
        *                      CTE or view on the preserved side of    *
        *                      OUTER JOIN, and this table expression,  *
        *                      CTE or view contains a correlated IN    *
        *                      subquery that DB2 may choose to         *
        *                      correlate/decorrelate.                  *
1       ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Performance may regress when an SQL statement contains a table
        expression, CTE or view on the preserved side of OUTER JOIN,
        and this table expression, CTE or view contains a correlated IN
        subquery that DB2 may choose to correlate/decorrelate.

         =========
          EXAMPLE
         =========

         WITH CTE1(C1, C2, C3) AS
           (SELECT C1, C2, C3
            FROM T1
            WHERE C1 IN (SELECT T2.C1
                         FROM T2
                         WHERE T1.C2 = T2.C2)
           )
         SELECT CTE1.C1, T3.C1
         FROM CTE1
              LEFT OUTER JOIN T3
              ON CTE1.C2 = T3.C2
              LEFT OUTER JOIN T4
              ON CTE1.C2 = T4.C2;

        DB2 may not choose to correlate/decorrelate the IN subquery for
        the above statement due to aggressive table expression/view
        merge, which may cause performance regression.

        DB2 code has been modified to handle the aforementioned
        performance issue. The aggressive table expression/view merge
        will not happen for a table expression, CTE or view on the
        preserved side of OUTER JOIN that contains a correlated IN
        subquery if an internal serviceability feature is disabled on
        your system under the suggestion of DB2 service.

        Additional keywords: SQLOUTERJOIN SQLOUTER SQLJOIN SQLLEFTJOIN
                             SQLLEFT SQLRIGHTJOIN SQLRIGHT SQLIN
                             SQLTABLEEXPR SQLSUBQUERY SQLCORRSUBQ
                             SQLPERFORMANCE SQLGLOBALOPT

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM82533
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        See PM82533 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM82533 corrects a problem of an SQL statement which contains a
        table expression, CTE or view that is used on the preserved side
        of OUTER JOIN, and this table expression, CTE or view contains
        a correlated IN subquery. DB2 may not choose to correlate/de-
        correlate the IN subquery due to aggressive table expression/
1       view merge, which may cause performance regression. After
        application of the PTF, when an internal serviceability feature
        is disabled on your system under the suggestion of DB2 service,
        the aggressive table expression/view merge will not happen for
        a table expression, CTE or view on the preserved side of OUTER
        JOIN that contains a correlated IN subquery.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF and the internal
        serviceability feature is disabled on your system. Review the
        PTF cover letter to determine which, if any, applications could
        be affected by this change.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOMTX  PM82533

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM82533   DSNXOMTX

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOMTX

      LISTEND
 UK93957 COVER LETTER END


 UK93974 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM84466 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of ALTER           *
        *                 TABLE ALTER COLUMN statement.                *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C4 RC0000003B in                  *
        *                      DSNXGRDS.DSNXOATV at OFFSET24AC         *
        *                      for an ALTER TABLE statement that       *
        *                      alters a base table which is used in    *
        *                      an inline table user defined function.  *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        ABEND0C4 RC0000003B in DSNXGRDS.DSNXOATV at OFFSET24AC
        for an ALTER TABLE statement that alters a base table which
        is used in an inline table user defined function.

        For Example,

         CREATE TABLE T1 (C1 CHAR(1));

         CREATE FUNCTION TUDF1(P1 INT, P2 INT)
            RETURNS TABLE(C1 CHAR(2))
            RETURN
             SELECT C1 FROM T1;

1       ALTER TABLE T1 ALTER COLUMN C1 SET DATA TYPE CHAR(10);

        An abend may occur for the ALTER statement above because DB2
        did not process the inline table user defined function that
        references to the altered table T1 correctly.
        DB2 was fixed to process the inline table user defined
        function that references to the altered table correctly.

        Additional KeyWords: SQLINLINE SQLTABLEUDF SQLALTER
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM84466
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOATV  PM84466

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM84466   DSNXOATV

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOATV

      LISTEND
 UK93974 COVER LETTER END


 UK93975 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM80685 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users                    *
        ****************************************************************
        * PROBLEM DESCRIPTION: Provide the ability to SELECT from      *
        *                      directory tables SYSIBM.DBDR and        *
        *                      SYSIBM.SPTR.                            *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        This APAR provides support for SQL SELECT from directory tables
        SYSIBM.DBDR and SYSIBM.SPTR.  This capability and the resulting
        output is primarily intended for use by IBM support.  The
        following restrictions apply:
        - The authorization rules that apply for selects against
          the catalog also apply for selects against directory
          objects. The authority must include one of the following:
          - Install SYSADM
          - SYSADM
          - SYSCTRL
          - ACCESSCTRL
          - DATAACCESS
          - SECADM
          - SQLADM
1         - System DBADM
          - DBADM on DSNDB01
          - select on a specific table
        - Only SELECT and FETCH are permitted.
        - No transaction L-locks will be acquired regardless of
          application isolation level.

        The ability to SELECT from directory objects is enabled when NFM
        (New Function Mode) is entered.  The ability to SELECT from the
        directory objects is not enabled in a new install.  For a new
        install or if DB2 is already in NFM when apar is applied it can
        be enabled by running a utility job:

        CATMAINT UPDATE UNLDDN PM80685


        To verify if the ability to SELECT from directory objects has
        been enabled, and the updates from this apar have been applied a
        row will be returned from the following SELECT:

        SELECT * FROM SYSIBM.SYSTABLESPACE
          WHERE DBNAME='DSNDB01' AND NAME='DBD01';
        ++HOLD for PM80685

        This apar provides the ability to update the catalog to allow
        selects from the directory tables DBDR and SPTR. To verify
        if the catalog has already been updated run the query:

        SELECT * FROM SYSIBM.SYSTABLESPACE
          WHERE DBNAME='DSNDB01' AND NAME='DBD01';

        The query will return one row if the catalog has been updated
        and zero rows if it has not been updated. If the query returns
        zero rows the catalog can be updated by running the utility job

        CATMAINT UPDATE UNLDDN PM80685

        The job will replace any existing catalog rows for directory
        objects that existed before the job is run.  This will
        invalidate packages that are dependent on the directory tables.

        The job is very quick and can be run at any time after applying
        the apar.  Running the job multiple times will not cause any
        problems.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM80685
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        This apar provides the ability to update the catalog to allow
        selects from the directory tables DBDR and SPTR. To verify
        if the catalog has already been updated run the query:

        SELECT * FROM SYSIBM.SYSTABLESPACE
          WHERE DBNAME='DSNDB01' AND NAME='DBD01';
1
        The query will return one row if the catalog has been updated
        and zero rows if it has not been updated. If the query returns
        zero rows the catalog can be updated by running the utility job

        CATMAINT UPDATE UNLDDN PM80685

        The job will replace any existing catalog rows for directory
        objects that existed before the job is run.  This will
        invalidate packages that are dependent on the directory tables.

        The job is very quick and can be run at any time after applying
        the apar.  Running the job multiple times will not cause any
        problems.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUECM0  PM80685
       DSNUECSE  PM80685

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM80685   DSNUECM0 DSNUECSE

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUECM0
       DSNUECSE

      LISTEND
 UK93975 COVER LETTER END


 UK93989 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM82438 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 10 for z/OS who use         *
        *                 IBM DB2 Analytics Accelerator and LOCAL      *
        *                 DATE FORMAT of dd/mm/yyyy                    *
        ****************************************************************
        * PROBLEM DESCRIPTION: Queries referencing an expression that  *
        *                      returns a LOCAL DATE format cannot      *
        *                      be offloaded                            *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        This APAR provides support for locally-defined DATE format of
        dd/mm/yyyy for users of IBM DB2 Analytics Accelerator so that
        queries referencing an expression that return a DATE data type
        are eligible for query offload.  The new DATE format to be
        allowed is dd/mm/yyyy.

        The new support for LOCAL DATE format is enabled using a new
        option, 4, to the DB2 subsystem parameter
        DSN6SPRM.QUERY_ACCEL_OPTIONS, which is used to specify
        additional types of SQL queries to be included in query
1       offloading.  The new option is:

          * 4   : The queries that reference an
                  expression with a DATE data type that
                  uses a LOCAL format are not blocked from
                  executing on IBM DB2 Analytics Accelerator.
                  IBM DB2 Analytics Accelerator will use the
                  dd/mm/yyyy format as LOCAL format.

                  The option 4 should be specified only when the
                  DATE FORMAT field of install panel DSNTIP4
                  specifies LOCAL or when application programs
                  that process SQL on DB2 have been precompiled
                  with the DATE(LOCAL) option.  In either case,
                  the LOCAL date exit routine must also define
                  the specific 'dd/mm/yyyy' date format.  If the
                  LOCAL format is not defined as 'dd/mm/yyyy',
                  the query may return unpredictable results.

        If option 4 is specified on any member in a data sharing
        environment, it is recommended to specify it on all members.

        See the HOLD information for additional details on this option.

        This APAR also adds a new reason code value 19 to indicate
        that the accelerator server driver level is downlevel for a
        specific function in the SQL statement.  The proper action is
        to update the accelerator server driver to the correct level
        to utilize the function in the SQL statement.

          New value for DSN_QUERYINFO_TABLE column REASON_CODE : 19
          ---------------------------------------------------------
          The accelerator server is not at the correct level and does
          not support a function in the SQL statement.  The column
          QI_DATA contains the function text or expression text
          that is using the unsupported function for the given
          accelerator server level. Update the accelerator
          server to enable offload of the SQL statement that
          contains the function text or expression text.

          Existing -4742 SQLCODE with a new reason code 19
          ------------------------------------------------
          The accelerator server is not at the correct level and
          does not support a function in the SQL statement.
          Update the accelerator server to enable offload of the
          SQL statement that contains the function text or
          expression text.

        Additional Keywords:
        IDAAV3R1/K SQLDATE
        Code has been added to support locally-defined DATE format
        of the form dd/mm/yyyy when option 4 is specified for
        DSN6SPRM.QUERY_ACCEL_OPTIONS, and the DATE FORMAT field of
        install panel DSNTIP4 specifies LOCAL or when application
        programs that process SQL on DB2 have been precompiled with
        the DATE(LOCAL) option.  In either case, the LOCAL date exit
1       routine must also define the specific 'dd/mm/yyyy' date format.

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM82438
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        ***Action for PM82438 (V10)

        System Requirements:
        To take advantage of the new LOCAL date format support
        for 'dd/mm/yyyy' on IBM DB2 Analytics Accelerator, the
        following fixes are needed in conjunction with this PTF:
        For IBM DB2 Analytics Accelerator, PM80112/UK93624 must
        be applied.
        For Netezza, level NZ 6.0.8 P-6 or higher is needed.

        This PTF adds a new option, 4, to the DB2 subsystem
        parameter DSN6SPRM.QUERY_ACCEL_OPTIONS, which is used
        to specify additional types of SQL queries to be included in
        query offloading.  The new option is:

          * 4   : The queries that reference an
                  expression with a DATE data type that
                  uses a LOCAL format are not blocked from
                  executing on IBM DB2 Analytics Accelerator.
                  IBM DB2 Analytics Accelerator will use the
                  dd/mm/yyyy format as LOCAL format.

                  The option 4 should be specified only when the
                  DATE FORMAT field of install panel DSNTIP4
                  specifies LOCAL or when application programs
                  that process SQL on DB2 have been precompiled
                  with the DATE(LOCAL) option.  In either case,
                  the LOCAL date exit routine must also define
                  the specific 'dd/mm/yyyy' date format.  If the
                  LOCAL format is not defined as 'dd/mm/yyyy',
                  the query may return unpredictable results.

        If option 4 is specified on any member of a data sharing
        environment, it is recommended to specify it on all members.

        NONE remains the default setting for QUERY_ACCEL_OPTIONS and is
        mutually exclusive from all other settings.  The options
        can be specified individually or together.  Examples:
          QUERY_ACCEL_OPTIONS=NONE
          QUERY_ACCEL_OPTIONS=1
          QUERY_ACCEL_OPTIONS=3
          QUERY_ACCEL_OPTIONS=(1,2)
          QUERY_ACCEL_OPTIONS=(1,3)
          QUERY_ACCEL_OPTIONS=(1,2,4)

        No action is required after applying this PTF unless both of
        the following are true:
          * The DSN6SPRM.ACCEL parameter is set to AUTO or COMMAND to
1           enable query acceleration.
          * The DSNHDECP.DATE parameter is set to LOCAL and the LOCAL
            date exit defines the specific dd/mm/yyyy date format.

        In that case, you need to take the following actions after
        applying this PTF:
        (1) Update your customized copy of job DSNTIJUZ
        (2) Update private copies of the DSNTIDxx CLIST input member

        Detailed guidance for these actions follows:
        ----------------------------------------------------------------
        (1) Update your customized copy of job DSNTIJUZ
        ----------------------------------------------------------------
        ==> This action is optional

            Update your customized copy of job DSNTIJUZ as follows:
            * Add or update the keyword parameter
                QUERY_ACCEL_OPTIONS=<y>
              where <y> is 4 or a list form such as (1,2,3,4) to the
              invocation of the DSN6SPRM macro.  Make sure to add a
              continuation character in column 72 if needed.  If your
              DSNTIJUZ job does not include QUERY_ACCEL_OPTIONS, that
              parameter will be set to the default of NONE 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.

        ----------------------------------------------------------------
        (2) Update private copies of the DSNTIDxx CLIST input member
        ----------------------------------------------------------------
        ==> This action is required only if you added or updated the
            setting for QUERY_ACCEL_OPTIONS in the previous step.

            If you added or modified the setting for
            QUERY_ACCEL_OPTIONS, you need to add or update the entry
            for it in all private copies of your CLIST output DSNTIDxx
            member.  In each such copy, add or update the following
            line:

            QUERY_ACCEL_OPTIONS CHAR  M  NONE        NONE          <y>

            Change <y> to the value you specified for
            QUERY_ACCEL_OPTIONS above in DSNTIJUZ.

            If you do not add QUERY_ACCEL_OPTIONS to a DSNTIDxx
            member, the DB2 installation CLIST will assume
            QUERY_ACCEL_OPTIONS=NONE when run with that member as
            input.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNDQWPZ  PM82438
       DSNDSPRM  PM82438
       DSNLDUMP  PM82438
       DSNLTEX1  PM82438
1      DSNLTGBK  PM82438
       DSNLTMIN  PM82438
       DSNLTSET  PM82438
       DSNLXRSQ  PM82438
       DSNWDFDI  PM82438
       DSNWZIFA  PM82438
       DSNXOD5   PM82438
       DSNXOEX1  PM82438
       DSNXONZA  PM82438
       DSNXONZQ  PM82438
       DSNXONZS  PM82438
       DSNXOOS1  PM82438
       DSNXROHB  PM82438
       DSNX8API  PM82438
       DSNX8EKG  PM82438
       DSNX8INI  PM82438
       DSNX8STA  PM82438
       DSN6SPRM  PM82438

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM82438   DSNDQWPZ DSNDSPRM DSNLDUMP DSNLTEX1 DSNLTGBK DSNLTMIN
                 DSNLTSET DSNLXRSQ DSNWDFDI DSNWZIFA DSNXOD5  DSNXOEX1
                 DSNXONZA DSNXONZQ DSNXONZS DSNXOOS1 DSNXROHB DSNX8API
                 DSNX8EKG DSNX8INI DSNX8STA DSN6SPRM

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNLDUMP
       DSNLTEX1
       DSNLTGBK
       DSNLTMIN
       DSNLTSET
       DSNLXRSQ
       DSNWDFDI
       DSNWZIFA
       DSNXOD5
       DSNXOEX1
       DSNXONZA
       DSNXONZQ
       DSNXONZS
       DSNXOOS1
       DSNXROHB
       DSNX8API
       DSNX8EKG
       DSNX8INI
       DSNX8STA

      MACROS
       DSNDQWPZ
       DSNDSPRM
       DSN6SPRM

      LISTEND
 UK93989 COVER LETTER END

1
 UK93990 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM81189 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS       *
        *                 users of created global temporary tables     *
        *                 (CGTTs).                                     *
        ****************************************************************
        * PROBLEM DESCRIPTION: Packages that use CGTTs are incorrectly *
        *                      invalidated during the DB2 10 ENFM      *
        *                      process. This will result in autobind   *
        *                      at next execution or require explicit   *
        *                      rebind. An invalidated package is not   *
        *                      saved as a plan management original or  *
        *                      previous and therefore cannot be used   *
        *                      with REBIND SWITCH.                     *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available and      *
        *                 follow the ++HOLD action.                    *
        ****************************************************************
        Dependencies are recorded in the SYSPKAGE catalog table space
        for all CGTTs (even though CGTTs are not truly dependent on
        anything in the SYSPKAGE table space). The SYSPKAGE catalog
        table space is dropped during DB2 10 for z/OS ENFM processing
        and all dependent packages are invalidated. Because we have
        these unnecessary package dependencies listed in the catalog
        for CGTTs we are invalidating more packages than we need to
        during the DB2 10 for z/OS ENFM process.

        Additional keywords: DB2MIGV10/K

        ++HOLD COMMENT FOR RELEASE 910, TYPE ACT:
        ***Action for PM81189 (V9)

        This PTF modifies V10 premigration checkout job DSNTIJPA.  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 DSNTIJPA
        - Delete all lines and copy in the DSNTIJPA member from the
          prefix.SDSNSAMP library
        - Follow the directions in the job prolog to customize it for
          your DB2
        - If you are preparing to migrate to DB2 V10, run the updated
          customized job to check for conditions that may affect your
          migration.


        ++HOLD COMMENT FOR RELEASE A10, TYPE ACT:
        ***Action for PM81189 (V10)

        This PTF modifies V10 premigration checkout job DSNTIJPM.
        If you maintain a customized copy of this job then after
        applying this PTF, you need to refresh it as follows:
        - Edit your customized copy of DSNTIJPM
        - Delete all lines and copy in the DSNTIJPM member from the
1         prefix.SDSNSAMP library
        - Follow the directions in the job prolog to customize it
          your DB2
        - If you are preparing to migrate to DB2 V10, run the updated
          customized job to check for conditions that may affect your
          migration.

        DB2 code has been changed so that CGTT packages will no longer
        show up as having dependencies on the SYSPKAGE catalog table
        space. This will eliminate unnecessary package invalidations
        during the DB2 10 for z/OS ENFM process.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM81189
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        ***Action for PM82100 (V10)

        This PTF modifies V10 premigration checkout job DSNTIJPM.
        If you maintain a customized copy of this job then after
        applying this PTF, you need to refresh it as follows:
        - Edit your customized copy of DSNTIJPM
        - Delete all lines and copy in the DSNTIJPM member from the
          prefix.SDSNSAMP library
        - Follow the directions in the job prolog to customize it
          your DB2
        - If you are preparing to migrate to DB2 V10, run the updated
          customized job to check for conditions that may affect your
          migration.
      ACTION:
        ***Action for PM81189 (V10)

        This PTF modifies V10 premigration checkout job DSNTIJPM.
        If you maintain a customized copy of this job then after
        applying this PTF, you need to refresh it as follows:
        - Edit your customized copy of DSNTIJPM
        - Delete all lines and copy in the DSNTIJPM member from the
          prefix.SDSNSAMP library
        - Follow the directions in the job prolog to customize it
          your DB2
        - If you are preparing to migrate to DB2 V10, run the updated
          customized job to check for conditions that may affect your
          migration.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNTIJPM  PM81189
       DSNXOTL   PM81189

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM81189   DSNTIJPM DSNXOTL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOTL
1
      MACROS
       DSNTIJPM

      LISTEND
 UK93990 COVER LETTER END


 UK94034 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM85671 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users with queries       *
        *                 involving partitioned tables with EQUAL on   *
        *                 host variables or parameter markers, and a   *
        *                 Data Partitioned Secondary Index (DPSI).     *
        ****************************************************************
        * PROBLEM DESCRIPTION: DB2 may choose a poorly performing      *
        *                      access path for a partitioned table     *
        *                      when:                                   *
        *                                                              *
        *                      1. DB2 uses an EQUAL predicate with     *
        *                      host variables or parameter markers to  *
        *                      limit the partitions for page range     *
        *                      access,                                 *
        *                                                              *
        *                      2. The PLAN_TABLE shows PAGE_RANGE='Y', *
        *                                                              *
        *                      3. There is at least one DPSI on the    *
        *                      table, and                              *
        *                                                              *
        *                      4. There is GROUP BY or ORDER BY in     *
        *                      the query.                              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        DB2 may choose a poorly performing access path for a partitioned
        table when DB2 uses an EQUAL predicate with a host variable or
        parameter marker to limit to only 1 partition for page range
        access, and the query also involves GROUP BY or ORDER BY.

        A sample query looks like this:

        SELECT ...
        FROM ...
        WHERE C1 = ?
        ORDER BY C2

        Data Partitioned Secondary Index on (C1,C2) with limit keys on
        C1 only.

        When the problem occurs, it might result in a poorly performing
        access path being selected by the DB2 optimizer.

        ADDITIONAL KEYWORDS: SQLACCESSPATH PERFM SQLHOSTVAR SQLGROUPBY
        PARAMETERMARKER SQLPMARKER SQLPMK PAGERANGE SQLORDERBY
1       With this logic corrected, DB2 can choose a more efficient
        access path for the situation described above.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM85671
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM85671:

        See PM85671 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM85671 corrects a problem of a poorly performing access path
        for a partitioned table when:
        1. DB2 uses an EQUAL predicate with host variables or parameter
           markers to limit the partitions for page range access,
        2. The PLAN_TABLE shows PAGE_RANGE='Y',
        3. There is at least one DPSI on the table, and
        4. There is a GROUP BY or ORDER BY in the query.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOGCX  PM85671
       DSNXOGOR  PM85671

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM85671   DSNXOGCX DSNXOGOR

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOGCX
       DSNXOGOR

      LISTEND
 UK94034 COVER LETTER END


 UK94056 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM78669 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS users of segmented table    *
        *                 spaces (either classic-segmented or          *
        *                 universal) who perform SQL mass delete       *
        *                 operations such as SQL DELETE without        *
        *                 predicate or TRUNCATE                        *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNISEGD ERQUAL500D *
        *                      during TRUNCATE TABLE or SQL DELETE     *
        *                      without predicate, on segmented table   *
1       ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        During a TRUNCATE TABLE or any similar operations that result in
        deletion of segments in a table, there are various checks to
        determine if the table space is physically opened. There was a
        timing window in the code in which the pageset open test was
        positive, but an asynchronous deferred close service task then
        physically closed the underlying pageset or partition. Later on
        when DB2 attempted to read a page, the effort failed with
        RC00C90101 DSNISEGD ERQUAL500D because the pageset/partition was
        now closed.

        The problem was that the abending module did not acquire a
        write claim early enough, which allowed the asynchronous
        deferred close service task to gain control of the pageset/
        partition.

        When run again, the TRUNCATE TABLE completed successfully.
        DB2 code has been corrected to ensure that there is a write
        claim on the object earlier in the code path, before bypassing
        the physical open of the pageset/partition.

        Additional keywords: SQLDELETE SQLTRUNCATE
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM78669
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNISEGD  PM78669

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM78669   DSNISEGD

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNISEGD

      LISTEND
 UK94056 COVER LETTER END


 UK94063 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM81712 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users who run RECOVER    *
        *                 utility with TOCOPY, TOLASTCOPY, or          *
        *                 TOLASTFULLCOPY.                              *
        ****************************************************************
        * PROBLEM DESCRIPTION: MSGDSNU1316I on RECOVER TOCOPY on       *
        *                      an object which is part of a set of     *
        *                      related objects.                        *
1       ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
          After migrating to DB2 10 for z/OS but while not yet in
        New Function Mode (NFM), user ran RECOVER TOCOPY utility on
        a single object which was part of a set of related objects.
          The job failed with DSNU1316I (TABLESPACES ARE MISSING FROM
        THE RECOVERY LIST) and the job ended RC8.  The problem applies
        to RECOVER with TOLASTCOPY and TOLASTFULLCOPY as well.
          This was due to VERIFYSET processing.  In DB2 10, the
        VERIFYSET function checks to ensure a point-in-time
        recovery includes all objects in a related set, and issues
        MSGDSNU1316I if it does not.
          If VERIFYSET is not specified on the RECOVER utility
        statement, VERIFYSET YES is assumed by default and the checking
        will take place.
          The VERIFYSET keyword is not supported in a utility statement
        prior to New Function Mode (NFM), so the problem could not
        be bypassed by specifying VERIFYSET NO.  When VERIFYSET NO
        was attempted it received MSGDSNU049I (INVALID OPERAND).
          Another problem is addressed by this APAR.  If VERIFYSET or
        ENFORCE is specified for a RECOVER job that is not to a prior
        point, MSGDSNU073I (KEYWORD IS IGNORED) is correctly issued
        and processing should continue.  But when this message was
        issued in these situations, RC8 was set and the job failed.
          DB2 utilities code was changed not to do VERIFYSET processing
        by default for RECOVER TOCOPY, RECOVER TOLASTCOPY, and
        RECOVER TOLASTFULLCOPY.  In addition, specifying VERIFYSET will
        not be allowed with these three RECOVER keywords.  Doing so
        will result in error message MSGDSNU052I (KEYWORD INCOMPATIBLE
        WITH OTHER KEYWORDS OR OPERANDS).  This is because these
        kinds of RECOVER invocations each allow only one object to be
        recovered, so in most cases it would not be possible to recover
        a set of objects in this way.
          Users are advised that RECOVER jobs with TOCOPY, TOLASTCOPY,
        or TOLASTFULLCOPY will now fail if VERIFYSET is specified.
          To support these changes the DB2 Utility Guide is updated.
        Under the RECOVER utility section, Syntax and options of the
        RECOVER control statement, the Syntax diagram is updated to
        reflect the proper usage and defaults for VERIFYSET.
        .
          Also, code was changed so that processing will continue when
        MSGDSNU073I is issued for a RECOVER to the current point due to
        VERIFYSET or ENFORCE being specified.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM81712
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
          After applying the fix for PM81712, specifying VERIFYSET will
        not be allowed for RECOVER utility using the keywords TOCOPY,
        TOLASTCOPY, or TOLASTFULLCOPY.  Doing so will result in error
        message MSGDSNU052I (KEYWORD INCOMPATIBLE WITH OTHER KEYWORDS
        OR OPERANDS).  This is because these kinds of RECOVER
        invocations each allow only one object to be recovered, so
1       in most cases it would not be possible to recover a set of
        objects in this way.
          Users are advised that RECOVER jobs with TOCOPY, TOLASTCOPY,
        or TOLASTFULLCOPY will now fail if VERIFYSET is specified.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUGDDL  PM81712

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM81712   DSNUGDDL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUGDDL

      LISTEND
 UK94063 COVER LETTER END


 UK94064 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM73217 -
        ****************************************************************
        * USERS AFFECTED: DB2 9 for z/OS and DB2 10 for z/OS users of  *
        *                 INSTEAD OF TRIGGERS                          *
        ****************************************************************
        * PROBLEM DESCRIPTION: Incorrect SQLCODE4735 when an INSTEAD   *
        *                      OF TRIGGER on a view invokes a stored   *
        *                      procedure and passes a transition       *
        *                      table.                                  *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When an INSTEAD OF TRIGGER (IO Trigger) that invokes a stored
        procedure and passes a transition table is executed, users may
        incorrectly see SQLCODE4735 with a wrapper SQLCODE723 on the
        executing statement.
        DB2 has been fixed to set the internal control blocks correctly
        when comparing the table locator reference with the transition
        table.

        Additional Keywords:
        SQLCODE4735
        SQLCODE723
        SQLTRIGGER
        SQLSP
        SQLSTOREDPROC
        SQLNATIVESQLPL
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM73217
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM69859:
1
        See PM69859 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM69859 corrects a problem of ABEND0C4 RC04 IN DSNIWNRF+1EBE
        when query contains a GROUP BY clause within a table expression
        or materialized view 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.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXISCR  PM73217
       DSNXOMW   PM73217

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM73217   DSNXISCR DSNXOMW

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXISCR
       DSNXOMW

      LISTEND
 UK94064 COVER LETTER END


 UK94071 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88481 -
        ****************************************************************
        * USERS AFFECTED: DB2 10 for z/OS REBUILD INDEX utility users. *
        ****************************************************************
        * PROBLEM DESCRIPTION: DB2 catalog table space                 *
        *                      DSNDB06.SYSTSTPT was recovered to a     *
        *                      point in time (PIT). All SYSTSTPT       *
        *                      indexes were put into the rebuild       *
        *                      pending (RBDP) state during RECOVER     *
        *                      utility PIT recovery processing. The    *
        *                      REBUILD INDEX of SYSTABLEPART index     *
        *                      DSNDPX01 abended as follows:            *
        *                                                              *
        *                        ABEND04E RC00C90205 DSNIOST2:504A     *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        During REBUILD INDEX processing DB2 utility code reads the
        SYSIBM.SYSTABLEPART catalog table row for the table that
        an index is on to get the AVGROWLEN column value. The DSNDPX01
        catalog index is used for these catalog table lookups. If the
        DSNDPX01 catalog index is in a rebuild pending state then this
        lookup fails with the noted abend:

1         ABEND04E RC00C90205 DSNIOST2 ERQUAL504A
        DB2 REBUILD INDEX utility code has been modified so that it will
        no longer try to read from the SYSTABLEPART catalog table when
        rebuilding an index on SYSTABLEPART. If the DSNDPX01 catalog
        is being rebuilt then DB2 utility code will now use other means
        to determine the average row length for SYSTABLEPART catalog
        table rows.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88481
    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  PM88481

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88481   DSNUCINM

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUCINM

      LISTEND
 UK94071 COVER LETTER END


 UK94086 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM83547 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users *
        *                 of REORG REBALANCE with a fieldproc defined  *
        *                 on a CHAR column used as the partitioning    *
        *                 key.                                         *
        ****************************************************************
        * PROBLEM DESCRIPTION: The external representation of the      *
        *                      LIMITKEY in SYSIBM.SYSTABLEPART is not  *
        *                      correct after a REORG REBALANCE on a    *
        *                      table where the partitioning key        *
        *                      consists of a CHAR column with a        *
        *                      FIELD PROCEDURE defined on it.          *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        A REORG REBALANCE was executed on a partitioned table space,
        where a FIELDPROC was defined on a CHAR column and it was the
        partitioning key of the table.  The REORG was successful but
        the external representation of the LIMITKEY in SYSTABLEPART
        was not correct.

        REORG invoked the FIELDPROC to decode the LIMITKEY of the CHAR
        column but incorrectly included a two byte length field as
        part of value to decode, corrupting the external value which
        was inserted into SYSTABLEPART.
1       REORG code has been modified to decode the CHAR LIMITKEY
        correctly.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM83547
    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  PM83547

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM83547   DSNUDALT

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUDALT

      LISTEND
 UK94086 COVER LETTER END


 UK94092 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86046 -
        ****************************************************************
        * USERS AFFECTED: All users of the DLDFREQ subsystem           *
        *                 parameter in DB2 10 for z/OS are affected    *
        *                 by this APAR.                                *
        ****************************************************************
        * PROBLEM DESCRIPTION: In DB2 10, the DLDFREQ parm accepts     *
        *                      settings other than NO, YES, and        *
        *                      integers from 0 - 32767.                *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        DLDFREQ specifies whether the level ID of a page set or
        partition is to be updated at DB2-determined checkpoint
        intervals.  Valid settings are ON and OFF but DLDFREQ also
        accepts a deprecated range of settings as integers from 0
1       through 32767 where 0 corresponds to OFF and 1 though 32767
        corresponds to ON.

        Currently, an error in DSN6SYSP permits DLDFREQ to accept
        values outside these ranges.  When this happens, DLDFREQ is
        effectively set to ON.

        In response, this APAR fixes DSN6SYSP so that DLDFREQ accepts
        only the documented settings of ON and OFF plus the deprecated
        settings of 0 - 32767.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM86046
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSN6SYSP  PM86046

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM86046   DSN6SYSP

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MACROS
       DSN6SYSP

      LISTEND
 UK94092 COVER LETTER END


 UK94094 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM85371 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 9 and 10 for z/OS.          *
        ****************************************************************
        * PROBLEM DESCRIPTION: Performance improvement for DSN1LOGP    *
        *                      utility using CHECK option.             *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        DSN1LOGP CHECK option suffers slow performance for large
        log ranges.
        The DSN1LOGP CHECK option has been modified to use a more
        efficient structure to increase performance.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM85371
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSN1LOGP  PM85371
       DSN1LOUT  PM85371

1     CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM85371   DSN1LOGP DSN1LOUT

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSN1LOGP
       DSN1LOUT

      LISTEND
 UK94094 COVER LETTER END


 UK94099 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM83092 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of RUNSTATS        *
        *                 utility with INCLUDE NPI                     *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNKBULD            *
        *                      ERQUAL5016 during a RUNSTATS utility    *
        *                      with INCLUDE NPI against an undefined   *
        *                      non-partitioned secondary index         *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        A RUNSTATS PART n USE PROFILE INCLUDE NPI executed against a
        table space with an undefined non-partitioned secondary
        index (NPSI). ABEND04E RC00C90101 at DSNKBULD:5016 occurred
        as the RUNSTATS tried to read keys from the underlying page set
        of the undefined NPSI.
        The RUNSTATS utility code has been modified to omit collecting
        any statistics for the undefined NPSI.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM83092
    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  PM83092

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM83092   DSNUSIIX

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUSIIX

      LISTEND
 UK94099 COVER LETTER END


 UK94119 COVER LETTER START
1   PROBLEM DESCRIPTION(S):
      PM80948 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 for z/OS 9 and 10.          *
        ****************************************************************
        * PROBLEM DESCRIPTION: 1. An IFI READS request causes ABEND0C4 *
        *                         in CSECT DSNWALCK.                   *
        *                                                              *
        *                      2. An invalid FROM CCSID may be used    *
        *                         when IFCID217 is written.            *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        1. If the size of the response area used for an IFI request is
        exactly the size of the return data, an incorrect pointer will
        be used by DB2 IFI code to update IFCA fields.  This will lead
        to an ABEND0C4 in CSECT DSNWALCK.

        2. When writing an IFCID217, DB2 may incorrectly determine the
        FROM CCSID to be used to convert the QW0217QA field to UTF.
        Dealing with an invalid CCSID, will cause a significant number
        of CPU cycles to be used by the conversion services.  This can
        lead to an increase of CPU cycles in the conversion services
        code.
        1. Correct the logic error for updating IFCA fields  when
        the response data equals the return area size.

        2. Correctly determine the FROM CCSID when writing IFCID217

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM80948
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNTXSTB  PM80948
       DSNWALCK  PM80948

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM80948   DSNTXSTB DSNWALCK

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNTXSTB
       DSNWALCK

      LISTEND
 UK94119 COVER LETTER END


 UK94142 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM81424 -
        ****************************************************************
1       * USERS AFFECTED: All DB2 10 for z/OS users of LOBs in         *
        *                 the distributed environment with the JCC T2  *
        *                 driver.                                      *
        ****************************************************************
        * PROBLEM DESCRIPTION: An ABEND04E RC00C90101 can occur at     *
        *                      location DSNOLMA2:5002 (ERQUAL5002) for *
        *                      a JAVA application that fetches a LOB   *
        *                      column using the JCC T2 driver in a     *
        *                      distributed environment.                *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An ABEND04E RC00C90101 can occur at location DSNOLMA2:5002
        (ERQUAL5002) when a JAVA application fetches a LOB column using
        the JCC T2 driver in a distributed environment.

        The abend occurs because DB2 fails to recognize a 'resource
        unavailable' condition when getting a page.  As a result, an
        internal abend was rendered instead of issuing an expected sql
        code -904 error (SQLCODE904).
        The code in DB2 is modified to prevent the abend and issue the
        SQLCODE -904 for the 'resource unavailable' condition.

        Additional Keywords: SQLCODE904 SQLLOB JCCT2ZOS
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM81424
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNOLMA2  PM81424

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM81424   DSNOLMA2

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNOLMA2

      LISTEND
 UK94142 COVER LETTER END


 UK94148 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM83218 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of Temporal        *
        *                 tables and after insert trigger              *
        ****************************************************************
        * PROBLEM DESCRIPTION: SQLCODE746 is incorrectly issued when   *
        *                      an insert statement on table 1          *
        *                      triggers an update on system period     *
        *                      temporal table 2 and the same           *
1       *                      transaction unit update or delete       *
        *                      table 2.                                *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        SQLCODE -746 is incorrectly issued when an insert
        statement on table 1 triggers an update on system period
        temporal table 2 and the same transaction unit updates or
        deletes table 2.

        Here is an example to illustrate the problem:
        1. Create table T1
        CREATE TABLE T1 ( EMPNO INT NOT NULL,
        LOCATION CHAR(20),
        COL3  CHAR(40) )

        2. Create temporal table T2
        CREATE TABLE T2 ( COUNTER   INT NOT NULL,
        LOCATION CHAR(20),
        SYS_START TIMESTAMP(12) NOT NULL GENERATED ALWAYS AS ROW BEGIN,
        SYS_END TIMESTAMP(12)   NOT NULL  GENERATED ALWAYS AS ROW END,
        CREATE_ID TIMESTAMP(12) NOT NULL GENERATED ALWAYS AS
        TRANSACTION START ID ,
        PERIOD  SYSTEM_TIME(SYS_START, SYS_END))

        3. Create history table T3
        CREATE TABLE T3 (COUNTER INT NOT NULL,
        LOCATION CHAR(20),
        SYS_START  TIMESTAMP(12) NOT NULL,
        SYS_END  TIMESTAMP(12) NOT NULL,
        CREATE_ID  TIMESTAMP(12) NOT NULL  )

        4. Insert into temporal table T2
        INSERT INTO  T2(COUNTER , LOCATION)
        VALUES( 0 ,'FRANKFURT' )
        INSERT INTO  T2(COUNTER , LOCATION)
        VALUES  ( 0 ,'MUENCHEN' )

        5. Create after insert trigger on T1
           Inside this trigger body, do update on temporal table T2
         CREATE TRIGGER TR1 AFTER  INSERT ON T1
           REFERENCING NEW AS NEU
           FOR EACH ROW MODE DB2SQL
           BEGIN ATOMIC
           UPDATE T2
           SET COUNTER= COUNTER + 1
           WHERE LOCATION = NEU.LOCATION ;
         END

         6. Alter table to add system versioning on table T2
         ALTER TABLE T2  ADD VERSIONING USE HISTORY TABLE T3

         7. Insert into table T1 which will fire the after insert
            trigger
         INSERT INTO T1 (EMPNO,LOCATION,COL3)
         VALUES( 1234 ,'FRANKFURT' ,'TEST1' )
1
         8. Delete from temporal table T2
         DELETE FROM T2 WHERE LOCATION = 'MUENCHEN'

         Instead of successfully delete one row from table T2,
         DB2 incorrectly issue sqlcode -746 for above Delete statement.



        DB2 has been modified to set flags correctly and
        process the update/delete statement successfully.

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM83218
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXTGS   PM83218
       DSNXTSTG  PM83218

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM83218   DSNXTGS  DSNXTSTG

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXTGS
       DSNXTSTG

      LISTEND
 UK94148 COVER LETTER END


 UK94150 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88170 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 for zOS.                    *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND522 or extended wait in DSNYAUTH   *
        *                      during allied address space IDENTIFY    *
        *                      processing.  The WAIT is on the         *
        *                      ASCEIECB ECB, which will not get        *
        *                      POSTed.                                 *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        During the first DB2 IDENTIFY from an allied address space,
        DSNYAUTH will POST the DB2 MSTR address space for cross memory
        authorization.  It will then WAIT on the ASCEIECB ECB.
        DSNYAUTH will set the request function code in the ASCE just
        before initializing the ASCEIECB ECB.  If DSNYAUTH gets
        interrupted and preempted right after the request function
        code is set in the ASCE, DB2 MSTR might see the ASCE with
1       the request function code, complete the cross memory
        authorization process and POST the ASCEIECB ECB before
        DSNYAUTH is re-dispatched in the allied address space.  This
        can result in DSNYAUTH initializing the ASCEIECB ECB after
        it was POSTed, resulting in a hang or ABEND522 on the
        subsequent WAIT on the ECB.
        DSNYAUTH has been changed to initialize the ASCEIECB ECB
        before setting the request function code in the ASCE to
        prevent this possible hang situation.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88170
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNYAUTH  PM88170

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88170   DSNYAUTH

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNYAUTH

      LISTEND
 UK94150 COVER LETTER END


 UK94222 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86167 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users who issue the      *
        *                 BIND QUERY command.                          *
        ****************************************************************
        * PROBLEM DESCRIPTION: After BIND QUERY, the BINDTIME column   *
        *                      in the SYSIBM.SYSQUERY table may show   *
        *                      an incorrect timestamp.                 *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        After BIND QUERY, the BINDTIME column in the SYSIBM.SYSQUERY
        table may show an incorrect timestamp because the value is not
        initialized to the current local timestamp.

        Additional Keywords:
        SQLTIMESTAMP BINDQUERY
        The problem is fixed by initializing the value to the current
        local timestamp.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM86167
    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
       DSNTBBNQ  PM86167
       DSNXOBNQ  PM86167

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM86167   DSNTBBNQ DSNXOBNQ

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNTBBNQ
       DSNXOBNQ

      LISTEND
 UK94222 COVER LETTER END


 UK94230 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM83404 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users who use  *
        *                 the GETHINT built-in function to retrieve    *
        *                 the hint for the password with which the     *
        *                 data were encrypted.                         *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00E70005 in DSNXRSBC P016    *
        *                      may occur when the GETHINT built-in     *
        *                      function is used to retrieve the hint   *
        *                      for the password with which the data    *
        *                      of a NOT NULL column were encrypted     *
        *                      but there was no hint specified during  *
        *                      data encryption.                        *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        ABEND04E RC00E70005 in DSNXRSBC P016 may occur when the GETHINT
        built-in function is used to retrieve the hint for the password
        with which the data of a NOT NULL column were encrypted but
        there was no hint specified during data encryption.

         =========
          EXAMPLE
         =========

         CREATE TABLE PM83404 (C1 CHAR(250) NOT NULL);

         -- set encryption password without hint
         SET ENCRYPTION PASSWORD ='Ben123';

         INSERT INTO PM83404 VALUES('ABCDEFGH') ;

         -- abend occurs
         SELECT GETHINT(ENCRYPT_TDES(C1)) FROM PM83404;

1       DB2 has incorrectly set the result nullability of GETHINT to
        NOT NULL when the argument is NOT NULL, which causes the abend
        and incorrect nullability information in DESCRIBE, DSNTIAUL
        sample program, and dynamic SQL processing programs such as
        SPUFI, DSNTEP2, and DSNTEP4. The result nullability of GETHINT
        should be 'nullable'.

        DB2 code has been modified to handle the GETHINT built-in
        function correctly.

        Additional keywords: SQLDECRYPT SQLENCRYPT SQLNULL SQLGETHINT

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM83404
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        See PM83404 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM83404 corrects a problem of ABEND04E RC00E70005 in DSNXRSBC
        P016 when the GETHINT built-in function is used to retrieve
        the hint for the password with which the data of a NOT NULL
        column were encrypted but there was no hint specified during
        data encryption.

        To make this fix effective for a static application, it must 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:
        PM83404 corrects a problem of ABEND04E RC00E70005 in DSNXRSBC
        P016 when the GETHINT built-in function is used to retrieve
        the hint for the password with which the data of a NOT NULL
        column were encrypted but there was no hint specified during
        data encryption.

        To make this fix effective for any view, column mask, or row
        permission defined on expressions that contain the GETHINT
        function, the object must be regenerated using the ALTER VIEW
        REGENERATE, ALTER MASK REGENERATE, or ALTER PERMISSION
        REGENERATE statement, respectively, or dropped and recreated
        after application of this PTF.

        To make this fix effective for any MQT, SQL scalar UDF, or
        index defined on expressions that contain the GETHINT
        function, the object must be dropped and recreated after
        application of this PTF.

        After application of the PTF, the nullability of the GETHINT
        scalar function may be different. Applications using DESCRIBE
        may be impacted. Proper actions should be taken if such impact
        is observed.

        If the DSNTIAUL sample program is used correctly to generate a
1       LOAD utility control statement, then after application of this
        PTF, the new control statement generated may not match the
        nullability of the GETHINT scalar functions from the previous
        control statement. Proper action should be taken if such
        mismatch is observed.

        This PTF affects the nullability of the GETHINT built-in scalar
        function returned by dynamic SQL processing programs, such as
        SPUFI, DSNTEP2, and DSNTEP4. Proper actions should be taken
        if such change is observed.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOBFA  PM83404

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM83404   DSNXOBFA

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOBFA

      LISTEND
 UK94230 COVER LETTER END


 UK94232 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88453 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS LOAD  *
        *                 utility users that try to load records into  *
        *                 a parent and child table in a referential    *
        *                 relationship simultaneously.                 *
        ****************************************************************
        * PROBLEM DESCRIPTION: The LOAD utility was used to load       *
        *                      records into both the parent and child  *
        *                      tables of a referential relationship    *
        *                      at the same time. This resulted in a    *
        *                      deadlock between the two LOAD utility   *
        *                      jobs.                                   *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available.         *
        ****************************************************************
        An attempt was made to load both the parent and child tables in
        a referential relationship at the same time. These jobs
        deadlocked in part because both of them needed to update the
        SYSTABLES.VERSION catalog table column. The LOAD utility code
        updates the SYSTABLES.VERSION catalog table column even when
        it's value has not changed.

        ABEND04E RC00C90088 DSNIDBLK OFFSET28E0
        MSGDSNT375I MSGDSNT500I DSNT375I
        DSNT500I
        DB2 utility code has been changed so that we will no longer
        update the SYSTABLES.VERSION catalog table column unless it
1       needs to be updated. If SYSTABLES.VERSION does need to be
        updated then there will still be a possibility that a deadlock
        will occur. Eliminating the unnecessary SYSTABLES.VERSION
        update in the catalog should greatly decrease the possibility
        of a deadlock when both parent and child tables are loaded at
        the same time. It will also provide a performance benefit in
        these non-update cases.

        The following utilities will also benefit from the changes made
        for this APAR:

            REPAIR VERSIONS, REORG, RECOVER, and MODIFY RECOVERY.

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88453
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUGUVR  PM88453

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88453   DSNUGUVR

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUGUVR

      LISTEND
 UK94232 COVER LETTER END


 UK94239 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM83853 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of current         *
        *                 TIMESTAMP with TIME ZONE  data in            *
        *                 an SQLPL Procedure.                          *
        ****************************************************************
        * PROBLEM DESCRIPTION: An incorrect result set can be returned *
        *                      from an SQLPL Procedure which           *
        *                      references TIMESTAMP with TIMEZONE      *
        *                      data.                                   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An incorrect result set can be returned from an SQLPL Procedure
        which references TIMESTAMP with TIME ZONE data.

        The following example illustrates such a failing case.

        STEP 1. Create an SQLPL Procedure that references TIMESTAMP
                with TIME ZONE data.
1
          CREATE PROCEDURE SC167601.SP_UNTYPEBU2 (
                                      OUT RESULT VARCHAR(32672),
                                      OUT P1 INT,
                                      OUT P2 CHAR(5),
                                      OUT P3 VARCHAR(32672))
          BEGIN
            DECLARE SQLSTATE CHAR(5);
            DECLARE SQLCODE  INT;
            DECLARE STMT VARCHAR(32672);

            DECLARE C1 CURSOR FOR STMT1 ;

         DECLARE EXIT HANDLER FOR SQLEXCEPTION
             BEGIN
             GET DIAGNOSTICS CONDITION 1
               P1  = DB2_RETURNED_SQLCODE,
               P2  = RETURNED_SQLSTATE,
               P3  = MESSAGE_TEXT;
             END;
           SET P3 = '';
           SET RESULT = '';

         SET STMT =
             'SELECT CAST(''9999-12-31 16:59:58.999999999999-07:00'' '||
             ' AS TIMESTAMP(12) WITH TIMEZONE)                       '||
             'FROM SYSIBM.SYSDUMMY1';

            PREPARE STMT1 FROM STMT;

            OPEN C1;

            FETCH C1 INTO RESULT;

            CLOSE C1;

           SET P1 = SQLCODE;
           SET P2 = SQLSTATE;
           SET P3 = '';
        END!


        STEP 2. Create a User-Defined Function (UDF) which calls the
                SQLPL Procedure.

          CREATE FUNCTION SC167601.UF_CALLSP2()
          RETURNS VARCHAR(32672)
          MODIFIES SQL DATA
          WLM ENVIRONMENT FOR DEBUG MODE WLMENV1
          BEGIN
            DECLARE P1 INT DEFAULT 999;
            DECLARE P2 CHAR(5) DEFAULT '';
            DECLARE P3 VARCHAR(32672) DEFAULT '';
            DECLARE CHECK INT;
            DECLARE RESULT VARCHAR(32672);

1           CALL SC167601.SP_UNTYPEBU2(RESULT, P1, P2, P3);
            SELECT LENGTH(RESULT) INTO CHECK
            FROM SYSIBM.SYSDUMMY1;

            IF CHECK <> 0 THEN
              RETURN RESULT;
            ELSE
              RETURN 'SQLCODE: '||CHAR(P1)||' SQLERR: '||P3;
            END IF;
          END!


        STEP 3. Declare a Temporary Table and import data using the UDF.

          DECLARE GLOBAL TEMPORARY TABLE TBQATEMP
            (C1 VARCHAR(32672));

          INSERT INTO SESSION.TBQATEMP VALUES (
          SC167601.UF_CALLSP2())


        STEP 4. Select from the Temporary Table.

         SELECT * FROM SESSION.TBQATEMP;

        An incorrect result (of zero) is returned.

         +------------------------------------------------------------
         |
         +------------------------------------------------------------
         | SQLCODE: 0           SQLERR:
         +------------------------------------------------------------

        The correct or expected result to be returned.
         +------------------------------------------------------------
         |
         +------------------------------------------------------------
         | 9999-12-31-16.59.58.999999999999-07:00
         +------------------------------------------------------------

        The code in DB2 has been modified to return the proper or
        expected result when referencing TIMESTAMP with TIME ZONE data.

        Additional Keywords : SQLNATIVESQLPL SQLTIMESTAMPTZ
                              SQLINCORR INCORROUT SQLINCORROUT
                              DB2INCORR/K

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM83853
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXROHB  PM83853
       DSNXROHR  PM83853
1      DSNXROHS  PM83853
       DSNXROH2  PM83853

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM83853   DSNXROHB DSNXROHR DSNXROHS DSNXROH2

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXROHB
       DSNXROHR
       DSNXROHS
       DSNXROH2

      LISTEND
 UK94239 COVER LETTER END


 UK94265 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM78193 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS users.                      *
        ****************************************************************
        * PROBLEM DESCRIPTION: A DB2 address space received an         *
        *                      ABEND04E RSN00F3040F because ACEs were  *
        *                      chained in a loop on a EOT queue.       *
        *                      This resulted in several CICS ABEND     *
        *                      U999.                                   *
        *                      RC00F3040F RSN00F3040F ABEND999         *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        A DB2 address space received an ABEND04E RSN00F3040F because
        ACEs were chained in a loop on a EOT queue.
        Module DSN3EOT0 has been updated to avoid the ABEND04E
        RSN00F3040F.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM78193
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSN3EOT0  PM78193

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM78193   DSN3EOT0

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSN3EOT0

      LISTEND
 UK94265 COVER LETTER END
1

 UK94283 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM85619 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of SET CURRENT     *
        *                 PACKAGESET.                                  *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C4 rc38 is incorrectly issued at  *
        *                      DSNXRIHB OFFSET 01A0 when SET CURRENT   *
        *                      PACKAGESET is executed with host        *
        *                      variable as the input.                  *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        ABEND0C4 rc38 is incorrectly issued at DSNXRIHB OFFSET 01A0 when
        SET CURRENT PACKAGESET is executed with host variable as the
        input.

        The following example illustrates the problem.

        Write an application SET CURRENT PACKAGESET

           DCL HCHAR CHAR(100) VARYING;

           HCHAR = 'TESTPATH';

           EXEC SQL SET CURRENT PACKAGESET = :HCHAR;

        The ABEND0C4 occurs when the SET statement is executed.  DB2
        code does not handle the internal structure correctly, and it
        leads to the ABEND.

        Please note, the following statements will also cause the
        similar ABEND above.

        EXEC SQL CONNECT TO STLEC1;

        EXEC SQL SET CURRENT ENCODING SCHEME = :HV;

        EXEC SQL SET CURRENT PACKAGE PATH = :HV;


        DB2 code has been fixed to address this problem.

        Additional Keywords: ABEND0C4
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM85619
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOLTD  PM85619
       DSNXRBIN  PM85619
1      DSNXRBI9  PM85619
       DSNXRDBC  PM85619
       DSNXRDB9  PM85619
       DSNXRIB9  PM85619
       DSNXRID9  PM85619
       DSNXRIHB  PM85619
       DSNXRIHD  PM85619
       DSNXRIHR  PM85619
       DSNXRIHS  PM85619
       DSNXRIS9  PM85619
       DSNXRSBC  PM85619
       DSNXRSB9  PM85619
       DSNXRTIM  PM85619
       DSNXRTI9  PM85619

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM85619   DSNXOLTD DSNXRBIN DSNXRBI9 DSNXRDBC DSNXRDB9 DSNXRIB9
                 DSNXRID9 DSNXRIHB DSNXRIHD DSNXRIHR DSNXRIHS DSNXRIS9
                 DSNXRSBC DSNXRSB9 DSNXRTIM DSNXRTI9

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOLTD
       DSNXRBIN
       DSNXRBI9
       DSNXRDBC
       DSNXRDB9
       DSNXRIB9
       DSNXRID9
       DSNXRIHB
       DSNXRIHD
       DSNXRIHR
       DSNXRIHS
       DSNXRIS9
       DSNXRSBC
       DSNXRSB9
       DSNXRTIM
       DSNXRTI9

      LISTEND
 UK94283 COVER LETTER END


 UK94311 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM84468 -
        ****************************************************************
        * USERS AFFECTED: DB2 10 for z/OS users using indexes.         *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C90101,LOC=DSNIDM.DSNICMT2 *
        *                      ERQUAL0000 during thread rollback.      *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Index manager allocates index look aside buffer when
1       traversing the index tree.
        A soft cancel occurred right after the index look
        aside buffer storage was allocated but before it was
        initialized. During abort processing, ABEND04E RC00C90101
        LOC=DSNIDM.DSNICMT2 ERQUAL0000 occurred when index manager
        was called to free cached index page using the
        uninitialized index look aside structure.
        Index manager code is changed to tolerate the uninitialized
        index look aside information during thread rollback.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM84468
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        This fix corrects an SQLCODE20356 error when a TRUNCATE TABLE
        operation is run on a parent table that is defined with an
        informational referential constraint by use of the NOT ENFORCED
        keywords on the references-clause of the CREATE or ALTER TABLE
        statement.

        Note that if TRUNCATE TABLE is run on parent tables for which
        all constraints are informational (NOT ENFORCED), the TRUNCATE
        will no longer be blocked. Such a condition should have been
        ignored by TRUNCATE TABLE.

        Customers making use of TRUNCATE TABLE can verify whether an
        object has only informational constraints defined by examining
        the ENFORCED column of the DB2 Catalog table SYSIBM.SYSRELS for
        the object being truncated.

        The DB2 Version 10 SQL REFERENCE manual under TRUNCATE
        statement "NOTES  Rules and restrictions" will be changed
        approximately as follows:
        "Rules and Restrictions: The truncate operation cannot be
        executed if the table is a parent table in an enforced
        referential constraint".
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNICLCU  PM84468
       DSNICMT2  PM84468
       DSNICUB   PM84468
       DSNIDALC  PM84468
       DSNIRSVP  PM84468
       DSNISDLE  PM84468
       DSNISRTI  PM84468
       DSNITCUS  PM84468
       DSNIXMDE  PM84468
       DSNKUNR2  PM84468

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM84468   DSNICLCU DSNICMT2 DSNICUB  DSNIDALC DSNIRSVP DSNISDLE
                 DSNISRTI DSNITCUS DSNIXMDE DSNKUNR2

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

1     MODULES
       DSNICLCU
       DSNICMT2
       DSNICUB
       DSNIDALC
       DSNIRSVP
       DSNISDLE
       DSNISRTI
       DSNITCUS
       DSNIXMDE
       DSNKUNR2

      LISTEND
 UK94311 COVER LETTER END


 UK94312 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM82054 -
        ****************************************************************
        * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
        ****************************************************************
        * PROBLEM DESCRIPTION: DSNL030I message from CSECT DSNLTSEC    *
        *                      may not properly identify origin of     *
        *                      the failed request.                     *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When an error is detected by DB2 CSECT DSNLTSEC, such as an
        authentication error, a DSNL030I message is issued to reflect
        the condition. The LUWID value is intended to refer to the
        adjacent remote system network address related to the failure
        however the LUWID value may actually refer to a network
        address that is not related to the failure. This can impede
        the user's ability to determine the origin of the failure and
        to correct the condition.
        The LUWID value may reflect an unrelated network address when
        the adjacent remote system operates in a gateway environment
        that services work from end users at different network
        addresses.
        When a user is successfully authenticated, at which point the
        end user's LUWID may be known, the LUWID value will now reflect
        the actual end user LUWID and hence its network address. If the
        gateway environment then assigns the connection (to DB2) to a
        different end user that encounters an error, such as a failed
        authentication, the DSNL030I message LUWID value will refer to
        the prior user and hence be misleading.

        When the remote system operates in a gateway environment, the
        network address of the actual end user causing the failure
        cannot yet be known because CSECT DSNLTSEC is involved at the
        very early stages of the access to DB2. It would however
        benefit users to always be aware of network address of the
        remote (gateway) system that's directly adjacent to DB2.
        However, with respect to IPv6 considerations, the LUWID value
        cannot fully reflect an IPv6 address of the adjacent partner.
1       As a result, the IP address of the adjacent partner will now
        be reflected in the "correlation token" component of the
        DSNLTSEC DSNL030I message THREAD-INFO information.
        Note: The LUWID value may still refer to a prior user and
          its address that may be unrelated to the failure.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM82054
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNLTSEC  PM82054

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM82054   DSNLTSEC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNLTSEC

      LISTEND
 UK94312 COVER LETTER END


 UK94352 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86946 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 and 10 users of CP parallelism.    *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00E50098 in DSNVEUS1         *
        *                      OFFSET1EFE when called by DSNTTTC       *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        During cleanup processing of CP query parallelism blocks, a
        timing window exists such that if an error occurred, residual
        information on the enclave used for the query may be left
        behind.  This can cause errors such as the symptom ABEND during
        the processing of later queries that run in parallel.
        The timing window noted above has been removed such that
        residual enclave information would not be left behind, even
        if an error were to occur.

        Additional diagnostic information is now recorded during CP
        parallelism's enclave processing.

        Additional keywords: SQLPARALLELISM
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM86946
    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
       DSNTTENE  PM86946
       DSNTTTGC  PM86946

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM86946   DSNTTENE DSNTTTGC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNTTENE
       DSNTTTGC

      LISTEND
 UK94352 COVER LETTER END


 UK94355 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86792 -
        ****************************************************************
        * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
        *                 DB2 10 for z/OS users only.                  *
        ****************************************************************
        * PROBLEM DESCRIPTION: Possible incorrect values reported      *
        *                      for the number of commit requests       *
        *                      received in the distributed activity    *
        *                      section of an accounting trace and      *
        *                      the distributed location section of     *
        *                      a statistics trace.                     *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Due to new function provided in DB2 10 for z/OS, some commit
        related accounting (DSNDQLAC) and statistics (DSNDQLST)
        counters were eliminated in favor of having the values be
        reflected in QLACCOMR and QLSTCOMR.
        A remote requester system establishes a (protected) Two phase
        commit connection with a DB2 for z/OS server.  During a commit
        sequence, the remote requester can transfer commit coordinator
        responsibility to the DB2 for z/OS server.  This essentially
        reflects a condition where DB2 for z/OS receives a commit
        request from the remote requester however DB2 10 for z/OS
        failed to account for this condition in QLACCOMR and QLSTCOMR.

        DB2 has been changed to correctly increment the number of
        commit requests received counter for the distributed
        activity information for an accounting trace (QLACCOMR) record
        and the distributed location sections of a statistics trace
        (QLSTCOMR) record.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM86792
    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
       DSNLTDRC  PM86792
       DSNLTPRC  PM86792

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM86792   DSNLTDRC DSNLTPRC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNLTDRC
       DSNLTPRC

      LISTEND
 UK94355 COVER LETTER END


 UK94357 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM87875 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of RUNSTATS        *
        *                 TABLESPACE utility collecting statistics     *
        *                 with UPDATE ALL or UPDATE SPACE specified.   *
        ****************************************************************
        * PROBLEM DESCRIPTION: INCORROUT SPACEF in MSGDSNU614I and     *
        *                      in SYSIBM.SYSTABLES catalog table.      *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        The user executed RUNSTATS TABLESPACE and the output showed
        incorrect SPACEF statistic in DSNU614I and in the
        SYSTABLES catalog table.

        The incorrect statistic value was caused by an overflow of
        the statistic value. This overflow was caused by using the
        32 bit Multiply Single assembler instruction generated
        by the compiler.
        Code was modified to allow the compiler to generate the 64 bit
        assembler instruction for the multiplication function.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM87875
    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  PM87875

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM87875   DSNUSEF2

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUSEF2
1
      LISTEND
 UK94357 COVER LETTER END


 UK94358 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM85306 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of pureXML         *
        ****************************************************************
        * PROBLEM DESCRIPTION: An ABEND04E at DSNNXML .DSNNQXCA:M128   *
        *                      might occur in response to a SQL        *
        *                      interrupt when DB2 is executing the     *
        *                      implicit or explicit XMLCAST function.  *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An ABEND04E at DSNNXML .DSNNQXCA:M128 might occur in response
        to a SQL interrupt when DB2 is executing the implicit or
        explicit XMLCAST function.

        When SQL interrupt is issued, DB2 will stop the processing
        of the SQL statement and issue SQLCODE. But the DSNNQXCA does
        not check the return code correctly. The ABEND occurs when the
        module continues and tries to use the invalid data.

        For example:
          Following query has an explicit XMLCAST function.

          SELECT MAX(LENGTH(XMLCAST(xmldoc AS VARCHAR(32000))))
          FROM T1;

          If the SQL interrupt is issued while XMLCAST is running, the
          ABEND04E at DSNNXML .DSNNQXCA:M128 will occur.
        DB2 is modified, so the SQL code is returned instead of issuing
        the ABEND04E at DSNNXML .DSNNQXCA:M128.

        Additional keywords: SQLXML XMLALL
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM85306
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNNQXCA  PM85306

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM85306   DSNNQXCA

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNNQXCA

1     LISTEND
 UK94358 COVER LETTER END


 UK94359 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88174 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS utility users of the     *
        *                 RUNSTATS utility with the PROFILE keyword.   *
        ****************************************************************
        * PROBLEM DESCRIPTION: Utility parsing incorrectly rejected    *
        *                      valid RUNSTATS SET PROFILE syntax with  *
        *                      various DSNU070I (KEYWORD OR OPERAND    *
        *                      INVALID) messages.                      *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When running RUNSTATS with the SET PROFILE keywords the
        customer intermittently received invalid error messages:

            RUNSTATS TABLESPACE A.B
                     TABLE (C.D)
                     COLUMN (E,F)
                     SET PROFILE

            DSNU070I KEYWORD OR OPERAND 'SET' INVALID WITH
                     'SET PROFILE'

            RUNSTATS TABLESPACE A.B
                     TABLE (C.D)
                     SET PROFILE FROM EXISTING STATS

            DSNU070I KEYWORD OR OPERAND 'EXISTING' INVALID WITH
                     'SET PROFILE'

        Other variations of the DSNU070I message which refer to
        UPDATE PROFILE, USE PROFILE and DELETE PROFILE are also
        possible.

        These problems were due to residual storage used by the utility
        parser.

        Additional search keywords:  MSGDSNU070I MSGDSNU070 DSNU070
        Code was added to initialize variables used by the RUNSTATS
        utility parser to detect invalid keyword combinations.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88174
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUGPPP  PM88174

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1      PM88174   DSNUGPPP

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUGPPP

      LISTEND
 UK94359 COVER LETTER END


 UK94383 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM85386 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS V8, DB2 9 for z/OS and DB2  *
        *                 10 for z/OS users of REORG and LOAD          *
        *                 utilities with inline statistics             *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00E40214 at DSNUSATS         *
        *                      OFFSET08F2 occurred when a LOAD utility *
        *                      with inline statistics failed to access *
        *                      SYSIBM.SYSTABSTATS table                *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When user ran multiple LOAD STATISTICS utilities concurrently,
        one of the LOAD jobs failed with an ABEND04E RC00E40214 after
        a catalog access error on SYSIBM.SYSTABSTATS due to deadlock
        between DSNDB06.SYSDBASE and DSNDB06.SYSSTATS.

        LOAD with inline statistics should skip the catalog update and
        issue MSGDSNU622I - CATALOG ACCESS FOR object-name NOT
        SUCCESSFUL, REASON=reason-code, and end with RC4 when catalog
        table SYSIBM.SYSTABSTATS access failed.
        The code has been modified to issue DSNU622I with RC4 when
        catalog access fails on SYSIBM.SYSTABSTATS when aggregating
        statistics for SYSIBM.SYSTABLESPACE.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM85386
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUSATS  PM85386

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM85386   DSNUSATS

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUSATS

      LISTEND
1UK94383 COVER LETTER END


 UK94397 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88340 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 for zOS.                    *
        ****************************************************************
        * PROBLEM DESCRIPTION: Loop in DSNRUDIS or restart status      *
        *                      table not displayed during DB2 restart  *
        *                      with a very large number of incomplete  *
        *                      Units of Recovery (URs).                *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        It is possible for DSNRUDIS to enter a loop or not to
        display the restart status table (following the DSNR007I
        message) during DB2 restart with a very large number of
        incomplete URs (approximately 410 or more).  If the
        message buffer size is greater than 32K, it can appear
        negative in DSNRUDIS causing incorrect loop control.  Although
        the loop is possible, the problem will most likely result
        in the restart status table not being displayed.
        Loop control has been corrected in DSNRUDIS.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88340
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNRUDIS  PM88340

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88340   DSNRUDIS

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNRUDIS

      LISTEND
 UK94397 COVER LETTER END


 UK94399 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM85784 -
        ****************************************************************
        * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
        ****************************************************************
        * PROBLEM DESCRIPTION: The following symptom may occur at a    *
        *                      DB2 for z/OS requester during a remote  *
        *                      bind of a DBRM that was generated by    *
        *                      DB2 V2R2 or earlier precompiler.        *
1       *                      . ABEND 0C4-00000004                    *
        *                        LOC=DSNXPA.DSNHCORE+0138              *
        *                        (ABEND0C4 RC00000004                  *
        *                         DSNXPA DSNHCORE OFFSET0138)          *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        A remote bind is performed with a DBRM that was generated by a
        DB2 V2R2 or earlier precompiler.  During bind processing, the
        DB2 requester system attempted to process the statements in the
        wrong CCSID, leading to the reported abend.

        DB2 requester system remote bind processing has been changed to
        use the correct CCSID when processing statements in such DBRMs.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM85784
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNLXRCM  PM85784

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM85784   DSNLXRCM

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNLXRCM

      LISTEND
 UK94399 COVER LETTER END


 UK94424 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM82573 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS users                       *
        *                                                              *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C4 RC0000003B at DSNXAAPC+1DC4    *
        *                      occurred during recovery processing     *
        *                      in the package authorization cache      *
        *                      recovery routine                        *
        *                                                              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        During DB2 recovery processing from a prior abend, an ABEND0C4
        in DSNXAAPC+1DC4 occurred in the package authorization cache
        program recovery routine. The abend occurred because an
        internal field used in the recovery processing was not
        initialized.

1       A similar abend can occur in the routine authorization cache
        program recovery module of DSNXAANC.

        Code has been changed to initialize the internal field
        correctly for package and routine authorization cache
        recovery purposes.

        Keywords: OFFSET1DCA

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM82573
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXAANC  PM82573
       DSNXAAPC  PM82573

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM82573   DSNXAANC DSNXAAPC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXAANC
       DSNXAAPC

      LISTEND
 UK94424 COVER LETTER END


 UK94426 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM85237 -
        ****************************************************************
        * USERS AFFECTED: DB2 for z/OS users utilizing sparse index    *
        *                 access.                                      *
        ****************************************************************
        * PROBLEM DESCRIPTION: Sometimes DB2 may generate the          *
        *                      following access path:                  *
        *                                                              *
        *                      1. Sparse index access is used          *
        *                      on a table, and                         *
        *                      2. Not all the applicable join          *
        *                      predicates are used for the             *
        *                      sparse index access in step 1.          *
        *                                                              *
        *                      When the conditions above are           *
        *                      met, incorrect output may occur         *
        *                      because the join predicates             *
        *                      described in step 2 may be              *
        *                      ignored sometimes due to dirty          *
        *                      storage.                                *
        *                                                              *
        *                      INCORROUT SQLINCORR                     *
1       *                      SQLINCORROUT DB2INCORR/K                *
        *                      SQLSPARSEINDEX SPARSEINDEX              *
        ****************************************************************
        * RECOMMENDATION: Sometimes DB2 may generate the following     *
        *                 access path.                                 *
        *                                                              *
        *                 1. Sparse index access is used on a table    *
        *                 2. Not all the applicable join predicates    *
        *                 are used for the sparse index access in      *
        *                 step 1.                                      *
        *                                                              *
        *                 When the conditions above are met,           *
        *                 incorrectout may occur because the join      *
        *                 predicates described in step 2 may be        *
        *                 ignored sometimes due to dirty storage.      *
        *                                                              *
        *                 For example,                                 *
        *                                                              *
        *                 SELECT *                                     *
        *                 FROM T1, T2                                  *
        *                 WHERE T1.C1 = T2.C1 AND                      *
        *                       T1.C2 = T2.C2;                         *
        *                                                              *
        *                                                              *
        *                 INCORRECTOUT may occur when the following    *
        *                 conditions are met.                          *
        *                 1. Sparse index access is used on the 2nd    *
        *                 table in the join sequence                   *
        *                 2. Only one predicate is used for the        *
        *                 sparse index access.                         *
        *                                                              *
        *                 When the conditions above are met, the       *
        *                 remaining predicate that is not used in      *
        *                 step 2 may be ignored by DB2 due to          *
        *                 dirty storage sometimes.                     *
        ****************************************************************
        Sometimes DB2 may generate the following access path:

        1. Sparse index access is used on a table, and
        2. Not all the applicable join predicates are used for the
        sparse index access in step 1.

        When the conditions above are met, incorrect output may occur
        because the join predicates described in step 2 may be
        ignored sometimes due to dirty storage.
        The incorrect output problem described above is fixed
        by marking the join predicates that are not used
        for the sparse index access as stage-2 predicates
        so that they will not be ignored.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM85237
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        See PM85237 APAR/PTF text for additional information about
1       why a REBIND is necessary.

        PM85237 corrects an incorrect output problem that may occur
        when (1) sparse index access is used on a table, and (2) not
        all the eligible join predicates are used for the sparse index
        key.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        A rebind is necessary for static applications to rebuild
        access paths based on the changes in this APAR.

        APAR PM75619 corrects two problems. The first problem occurs
        on both V9 and V10.  A query may produce incorrect output
        when a UNICODE table joins to an EBCDIC view which is a
        UNION ALL, and at the same time, when index-on-expression
        (IOE) is used for that query.  The second problem occurs on V10
        only.  DB2 may not issue a REORG suggestion as it should.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        A rebind is necessary for static applications to rebuild
        access paths based on changes in this APAR.

        PM63095 corrects a problem of ABEND04E RC00C90101 in
        DSNIPSFI :5007 when executing an SQL statement containing
        a User Defined Function (UDF) with the DISALLOW PARALLEL
        parameter while parallelism is enabled.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOGP   PM85237

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM85237   DSNXOGP

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOGP

      LISTEND
 UK94426 COVER LETTER END


 UK94446 COVER LETTER START
1   PROBLEM DESCRIPTION(S):
      PM83507 -
        ****************************************************************
        * USERS AFFECTED: DB2 V10 users                                *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00E2000C in DSNSVSVB         *
        *                      followed by DB2 down with RC00E50702    *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When a data set is physically closed, its main control
        block and an extension control block are released if the
        data set has no pages cached in a buffer pool. Otherwise,
        those control blocks are not released and the main control
        block is chained in a list. When a DB2 checkpoint process
        removes all cached pages, those control blocks are released.
        However, the extension block is not released with the main
        control block. This only affects linear data sets in V10
        since V10 allocates the extension control block of linear
        data sets on a separate location, from where the main data set
        control block is allocated.
        DB2 checkpoint logic has been modified to release the extension
        control block of linear data sets when they do not have pages
        cached in buffer pools.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM83507
    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  PM83507

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM83507   DSNB1CHK

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNB1CHK

      LISTEND
 UK94446 COVER LETTER END


 UK94457 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM70646 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of native SQL      *
        *                 procedure and non-inline SQL scalar          *
        *                 function.                                    *
        ****************************************************************
        * PROBLEM DESCRIPTION: An ABEND04E at location                 *
        *                      DSNXGRDS DSNXOYPL M210 may occur when   *
        *                      more than one assignment is included    *
1       *                      in the same assignment statement in the *
        *                      native SQL procedure or non-inline SQL  *
        *                      scalar function which goes through      *
        *                      either rebind, incremental rebind or    *
        *                      deploy route.                           *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An ABEND04E at location DSNXGRDS DSNXOYPL M210 may occur when
        the native SQL procedure or non-inline SQL scalar function that
        contains an assignment statement which includes more than one
        assignment (multiple assignments) goes through either rebind,
        incremental rebind or deploy route.


        EXAMPLE
        =======

        CREATE PROCEDURE ADMF001.MYPROC()
        LANGUAGE SQL
        BEGIN
          DECLARE V1 INTEGER;
          DECLARE V2 TIMESTAMP;

          SET V1 = 1,
              V2 = CURRENT TIMESTAMP;

        END!

        REBIND PACKAGE(ADMF001.MYPROC.(*))!

        DB2 is updated to process multiple assignments correctly in
        SQL native procedure and non-inline SQL scalar function that go
        through the rebind, incremental rebind, or deploy route.

        Additional Keywords: SQLNATIVESQLPL

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM70646
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOYPL  PM70646

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM70646   DSNXOYPL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOYPL

      LISTEND
 UK94457 COVER LETTER END
1

 UK94459 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM84769 -
        ****************************************************************
        * USERS AFFECTED: ALL DB2 users using ARRAY_EXISTS, ROLLUP,    *
        *                 or CUBE as SQL identifiers (object names)    *
        ****************************************************************
        * PROBLEM DESCRIPTION: New syntax support in newer release     *
        *                      of DB2 will most likely introduce       *
        *                      new reserved words.                     *
        *                      Among them, most are softened,          *
        *                      while some or a few cannot be softened  *
        *                      within certain SQL contexts due to      *
        *                      ambiguity.                              *
        *                      Customers are faced with potential      *
        *                      problems on existing object names       *
        *                      once they have migrated to the newer    *
        *                      release.                                *
        *                                                              *
        *                      While circumventions are provided,      *
        *                      such as using a delimited identifier in *
        *                      the newer release, this APAR            *
        *                      provides an early detection on DB2      *
        *                      10 for z/OS (V10)                       *
        *                      prior to the migration to the next      *
        *                      release of DB2.                         *
        *                      It allows customers to act upon and     *
        *                      to fix the problem ahead  of the        *
        *                      migration.                              *
        *                                                              *
        *                      This APAR is only applicable on V10     *
        *                      and serves as an                        *
        *                      early detection aid by providing        *
        *                      IFCID 0366 trace records.               *
        *                                                              *
        *                      There are three new reserved words      *
        *                      being identified which may cause        *
        *                      incompatibilities depending on context. *
        *                                                              *
        *                      The three words are:                    *
        *                      ARRAY_EXISTS, CUBE, and ROLLUP.         *
        *                                                              *
        *                                                              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************

        Here is an illustration of the problem the customer might
        face after migrating to the next release after DB2 10 for z/OS
        (V10).

        A V10 application could have created a user-defined function
        named ARRAY_EXISTS, and could have an SQL statement invoking
        the function as follows:
1
        SELECT X FROM T WHERE ARRAY_EXISTS(Y,2) = 2;

        In the next release of DB2,
        ARRAY_EXISTS is the name of a new predicate via a new
        SQL support, and in a similar SQL construct, ARRAY_EXISTS will
        be treated as the new predicate and it can not map to
        the user-defined function that the user anticipated as if it
        were in V10.

        Similar problems exist for the new reserved words, CUBE and
        ROLLUP when they are used as an unqualified ordinary identifier
        for a user-defined function name.

        When the customer enables the IFCID 0366 trace while they are
        on V10,  and if the usage of the above three reserved words are
        detected, DB2 will produce the following IFCID 0366 trace
        records indicated by the three new values in the QW0366FN field.

        QW0366FN = 4
        A QW0366FN 4 record indicates that the statement uses the word
        ARRAY_EXISTS as an unqualified user-defined function name in a
        context that may be incompatible with the release after V10.

        This value is issued in V10 only.

        QW0366FN = 5
        A QW0366FN 5 record indicates that the statement uses the word
        CUBE as an unqualified user-defined function name in a
        context that may be incompatible with the release after V10.
        This value is issued in V10 only.

        QW0366FN = 6
        A QW0366FN 6 record indicates that the statement uses the word
        ROLLUP as an unqualified user-defined function name in a
        context that may be incompatible with the release after V10.
        This value is issued in V10 only.

        From the IFCID 0366 trace records collected, if QW0366FN
        has values, 4,5, or 6, then adjustments to the application
        should be made to avoid the conflict - either by changing the
        word to a delimited identifier, or by changing the word to
        a name that is not reserved in the release after V10.

        For example:
         ARRAY_EXISTS1 in place of ARRAY_EXISTS.

        For CUBE and ROLLUP, in addition to the above recommended
        circumvention, the reference can be qualified to avoid
        the conflict.
        This is a new feature in V10 and is only available and has
        meaning on V10. It can be run on either NFM or CM mode.

        Once migrated on to the next release after V10, no IFCID 0366
        record will be issued for the three words above
        since the three new words will subject
1       to syntax validation based on all syntax
        for the next release.



    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM84769
    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  PM84769
       DSNHSMF3  PM84769
       DSNXRTIM  PM84769

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM84769   DSNDQW05 DSNHSMF3 DSNXRTIM

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNHSMF3
       DSNXRTIM

      MACROS
       DSNDQW05

      LISTEND
 UK94459 COVER LETTER END


 UK94460 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86225 -
        ****************************************************************
        * USERS AFFECTED: Users of DB2 for z/OS executing a            *
        *                 REMOTE BIND/REBIND across different          *
        *                 subsystem versions.                          *
        ****************************************************************
        * PROBLEM DESCRIPTION: THE PROBLEM THIS FIX ADDRESSES HAS THE  *
        *                      FOLLOWING REPORTED SYMPTOMS:            *
        *                                                              *
        *                          ABEND0C4 RC00000010                 *
        *                           CSECT DSNSVBK OFFSET0E16           *
        *                                                              *
        *                          also possible is                    *
        *                                                              *
        *                          Incorrect error messages when       *
        *                          using a new V10 function on a       *
        *                          previous version subsystem          *
        *                          like V9                             *
        *                                                              *
        *                      PROBLEM SCENARIO:                       *
        *                                                              *
        *                      The reported error occurred when        *
1       *                      attempting a REMOTE BIND from a V10     *
        *                      subsystem to a V9 subsystem. An         *
        *                      overlay can occur causing the said      *
        *                      abend.                                  *
        *                                                              *
        *                      Additionally, an incorrect error        *
        *                      message can occur when using a new      *
        *                      V10 bind parameter with a previous      *
        *                      version subsystem.                      *
        *                      Here is an example:                     *
        *                                                              *
        *                      Binding from a V10 subsystem to a       *
        *                      V9 subsystem using the 'APCOMPARE'      *
        *                      parameter might give you an 'invalid    *
        *                      keyword' error instead of message       *
        *                      DSNT263I - csect-name bind-type FOR     *
        *                      object-type = object-name FAILED        *
        *                      BECAUSE THE bind-type DEPENDS ON        *
        *                      FUNCTIONS IN A LATER DB2 RELEASE        *
        *                      WITH MARK release-dependency-mark       *
        *                      OR HIGHER.                              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        SUMMARY OF DB2 EVENTS:
        When executing the BIND from a V10 subsystem, DB2 used storage
        in a control block that was not a compatible size with the V9
        DB2 subsystem and subsequently overlaid other storage causing
        the abend.
        Additionally, DB2 could use the wrong message handler when
        a new bind parameter from V10 is passed to a subsystem on a
        previous DB2 release.
        PROBLEM CONCLUSION:
        DB2 V9 is fixed so that the control block used for the
        BIND/REBIND is now a compatible size across subsystems.
        Also, in V10, the error messages have been changed to display
        the correct message when a new V10 bind parameter is used on
        a subsystem running a previous release of DB2.

        ADDITIONAL KEYWORDS:
        BIND REBIND SQLSTORAGE DB2COEXIST/K DB2OVRLAY/K
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM86225
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        This fix should be applied to V10 subsystems to handle
        the problem where inaccurate error messages could be
        issued when attempting to use new V10 bind parameters on
        previous version subsystems.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNECP40  PM86225
       DSNECP41  PM86225
       DSNECP44  PM86225
1      DSNECP45  PM86225
       DSNECP47  PM86225

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM86225   DSNECP40 DSNECP41 DSNECP44 DSNECP45 DSNECP47

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNECP40
       DSNECP41
       DSNECP44
       DSNECP45
       DSNECP47

      LISTEND
 UK94460 COVER LETTER END


 UK94462 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM87084 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS users whose query contains  *
        *                 ORDER BY and an OMNIFIND function.           *
        ****************************************************************
        * PROBLEM DESCRIPTION: DB2 may meet incorrect output if the    *
        *                      query satisfies the following           *
        *                      conditions:                             *
        *                                                              *
        *                      1. The query refers to a table with an  *
        *                         OMNIFIND function.                   *
        *                      2. The table with OMNIFIND function is  *
        *                         the leading table with a unique      *
        *                         index.                               *
        *                      3. The columns for ORDER BY are from    *
        *                         this table.                          *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        DB2 may meet incorrect output when the query with an ORDER BY
        clause refers to a table with an OMNIFIND function.


        ADDITIONAL KEYWORDS:
        SQLORDERBY  SQLOMNIFIND  SQLINCORROUT SQLINCORR
        INCORROUT DB2INCORR/K
        The problems mentioned above are fixed so that DB2 will not
        meet incorrect output again.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM87084
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM87084:
1
        See PM87084 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM87084 corrects a problem of incorrect output for a query
        with an ORDER BY clause that refers to a table with an
        OMNIFIND function.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOTS   PM87084

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM87084   DSNXOTS

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOTS

      LISTEND
 UK94462 COVER LETTER END


 UK94483 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86984 -
        ****************************************************************
        * USERS AFFECTED: DB2 10 for z/OS users using index insert     *
        *                 I/O parallelism.                             *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C90206 DSNIIDIS ERQUAL5002 *
        *                      happened during SQL DELETE operation.   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        During SQL INSERT execution, index I/O parallelism could be used
        when there are three or more indexes defined on the table being
        inserted into.

        When index insert I/O parallelism is in use, if I/O wait is
        encountered on the clustering index get page request,
        index tree traversal will exit early without fully
        populating the index look aside buffer with correct information.

        In a very small timing window, the index look aside buffer
        already contains residual information before the index tree
        traversal starts. Index insert I/O parallelism will leave
        residual information in the index look aside buffer after the
        insert finishes. The subsequent SQL INSERT using the index look
        aside buffer causes the index key to be inserted into the wrong
        leaf page. This problem only happens when inserting into the
1       clustering index.

        Later on, SQL DELETE detects the problem by issuing ABEND04E
        RC00C90206 DSNIIDIS ERQUAL5002. CHECK INDEX utility can also
        detect the error if it is run with DIAGNOSE TYPE(70,71).
        Index needs to be rebuilt to correct the error.
        DB2 code was modified to make sure there is no residual
        information left in the index look aside buffer after SQL
        INSERT when index insert I/O parallelism is in use.


        Additional keywords: SQLINSERT
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM86984
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNKTRAV  PM86984

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM86984   DSNKTRAV

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNKTRAV

      LISTEND
 UK94483 COVER LETTER END


 UK94499 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM87742 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS utility users of the     *
        *                 RECOVER utility                              *
        ****************************************************************
        * PROBLEM DESCRIPTION: Serviceability                          *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        Serviceability
        Serviceability
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM87742
    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  PM87742
       DSNUCALZ  PM87742
       DSNUCBDR  PM87742
1
      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM87742   DSNUCAIN DSNUCALZ DSNUCBDR

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUCAIN
       DSNUCALZ
       DSNUCBDR

      LISTEND
 UK94499 COVER LETTER END


 UK94503 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86013 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS       *
        *                 users of BACKUP SYSTEM, RESTORE SYSTEM,      *
        *                 and RECOVER utilities running on a system    *
        *                 with z/OS V2.1 or above.                     *
        ****************************************************************
        * PROBLEM DESCRIPTION: BACKUP SYSTEM, RESTORE SYSTEM, and      *
        *                      RECOVER utilities receive               *
        *                      MSGDSNU1608I with RC8 on systems        *
        *                      running z/OS V2.1 or above.             *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
          Certain functions of BACKUP SYSTEM utility, RESTORE SYSTEM
        utility, and RECOVER utility receive
        DSNU1608I - UTILITY FAILED.  REQUIRED DFSMSHSM SERVICES NOT
                    AVAILABLE
        and cause the utility to fail with RC8.
          This message is issued when DB2 detects that the level of
        z/OS does not support the function(s) needed by the utility
        to continue as requested.
          Users running z/OS V2.1 or above could see this message issued
        and the utility job unexpectedly terminated even though this
        level of z/OS does support all functions for which this
        detection is currently done.
          The logic to ascertain the level of z/OS running was in error,
        and falsely triggered the message and the failure of the job.
          Code was changed in BACKUP SYSTEM utility, RESTORE SYSTEM
        utility, and RECOVER utility to correctly determine the z/OS
        version that is running and assess its support of DB2
        functionality accordingly.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM86013
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DOCUMENTATION:
        PM63884 adds a documentation change in Utility Guide and
1       Reference like the following:

        In Chapter 28. RESTORE SYSTEM,Utility Guide and Reference V10.
        Under the section "Authorization required":

          This RACF authority is required, because the RESTORE
          SYSTEM utility invokes DFSMSdss when tape is the input
        | and z/OS level is 1.11(or lower). However, when you
        | restore database copy pools from tape when z/OS level is
        | 1.12(or higher) or from a FlashCopy on disk, the RESTORE
          SYSTEM utility invokes DFSMShsm, which does not require
          Operations or DASDVOL authority.

        Chapter 28. RESTORE SYSTEM
        Under the section "How to determine which system-level backups
        DB2 restores":

        | The RESTORE SYSTEM utility invokes DFSMShsm to restore the
          database copy pool volumes from a system-level backup on
        | tape when running z/OS 1.12 or above. Otherwise, it invokes
        | DFSMSdss.
      ACTION:
        After applying the fix for PM63384, users are advised that
        the job output of RESTORE SYSTEM utility from tape might not
        include DFSMSdss messages in cases where DFSMShsm is now
        called instead.
        This PTF has changed RESTORE SYSTEM to call DFSMShsm to
        invoke DFSMSdss in its own address space (cross memory mode, XM)
         instead of DFSMShsm's address space when z/OS level is 1.12 or
        later.
        THE FOLLOWING IMPORTANT ACTION IS REQUIRED:
        APPLY HSM APAR OA40046 BEFORE OR AT THE SAME TIME PM63384 IS
        APPLIED. FAILURE TO DO SO CAN RESULT IN A FAILURE OF RESTORE
        SYSTEM IF PM63384 IS APPLIED AND ACTIVE ON DB2 BUT OA40046 IS
        NOT APPLIED AND ACTIVE ON HSM.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUCBDR  PM86013
       DSNUGUTC  PM86013
       DSNUVBBD  PM86013
       DSNUVBRD  PM86013

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM86013   DSNUCBDR DSNUGUTC DSNUVBBD DSNUVBRD

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUCBDR
       DSNUGUTC
       DSNUVBBD
       DSNUVBRD

      LISTEND
 UK94503 COVER LETTER END

1
 UK94511 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM83370 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of the DB2 trace,  *
        *                 IFCIDs 58 and 401.                           *
        ****************************************************************
        * PROBLEM DESCRIPTION: For the DB2 trace, the IFCID 401 trace  *
        *                      record (fields QW0401IX and QW0401TB)   *
        *                      and the IFCID 58 trace record (fields   *
        *                      QW0058IS and QW0058TB) can provide      *
        *                      incorrect count values for the number   *
        *                      of index scans and the number of        *
        *                      tablespace scans respectively.          *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        For the DB2 trace, the IFCID 401 trace record (fields QW0401IX
        and QW0401TB) and the IFCID 58 trace record (fields QW0058IS and
        QW0058TB) can provide incorrect count values for the number of
        index scans and the number of tablespace scans respectively.

        The number of index scans and the number of tablespace scans
        can be recorded incorrectly for IFCID 58 and IFCID 401 trace
        records.

        The DB2 performance trace record for IFCID 58 can contain
        incorrect values for the following fields:

          1. QW0058IS             NUMBER OF INDEX SCANS.
          2. QW0058TB             NUMBER OF TABLE SPACE SCANS.


        The DB2 monitor trace record for IFCID 401 can contain
        incorrect values for the following fields:

          1. QW0401IX             NUMBER OF INDEX SCANS.
          2. QW0401TB             NUMBER OF TABLE SPACE SCANS.


        The following example helps illustrate the problem.
        Given the following SQL statement.

          EXEC SQL
           SELECT LASTNAME INTO :HVC
           FROM EMP
           WHERE EMPNO =  000170;

        Using EXPLAIN, the above query is shown to use index access
        (ACCESSTYPE='I').

        When a performance trace for IFCID 58 is activated, both the
        QW0058IS and QW0058TB fields for the above statement are non-
        zero.

1         QW0058IS = 1
          QW0058TB = 1

        When a monitor trace for IFCID 401 is activated, both the
        QW0401IX and QW0401TB fields for the above statement are zero.

          QW0401IX = 0
          QW0401TB = 0


        Please note that for the above statement, only fields for index
        scans are expected to be non-zero.  The fields for tablespace
        scans are expected to be 0.

        QW0058IS = 1
        QW0058TB = 0

        QW0401IX = 1
        QW0401TB = 0

        DB2 is modified to update the trace counters correctly.

        Additional Keywords: IFCID401 IFCID058 INCORROUT
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM83370
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXERT   PM83370
       DSNXREOJ  PM83370
       DSNXREO9  PM83370
       DSNXRFF   PM83370
       DSNXRFF9  PM83370
       DSNXRFN   PM83370
       DSNXRFN9  PM83370
       DSNXROJ1  PM83370
       DSNXROJ9  PM83370
       DSNXRSFN  PM83370
       DSNXRSGB  PM83370
       DSNXRSG9  PM83370
       DSNXRSN9  PM83370
       DSNXRT1J  PM83370
       DSNXRT19  PM83370
       DSNXSBUC  PM83370
       DSNXSIND  PM83370
       DSNXSING  PM83370

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM83370   DSNXERT  DSNXREOJ DSNXREO9 DSNXRFF  DSNXRFF9 DSNXRFN
                 DSNXRFN9 DSNXROJ1 DSNXROJ9 DSNXRSFN DSNXRSGB DSNXRSG9
                 DSNXRSN9 DSNXRT1J DSNXRT19 DSNXSBUC DSNXSIND DSNXSING

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

1     MODULES
       DSNXERT
       DSNXREOJ
       DSNXREO9
       DSNXRFF
       DSNXRFF9
       DSNXRFN
       DSNXRFN9
       DSNXROJ1
       DSNXROJ9
       DSNXRSFN
       DSNXRSGB
       DSNXRSG9
       DSNXRSN9
       DSNXRT1J
       DSNXRT19
       DSNXSBUC
       DSNXSIND
       DSNXSING

      LISTEND
 UK94511 COVER LETTER END


 UK94512 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88781 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS subsystems running       *
        *                 the DSNTIJEN job.                            *
        ****************************************************************
        * PROBLEM DESCRIPTION: If the DB2 10 for z/OS ENFM process     *
        *                      (job DSNTIJEN) is run when there are    *
        *                      stopped utilities, then subsequent      *
        *                      REORG, LOAD REPLACE, and LOAD RESUME    *
        *                      jobs against these objects involved     *
        *                      with the stopped utilities may abend    *
        *                      as follows:                             *
        *                                                              *
        *                      ABEND04E RC00C90101 DSNIDBMF ERQUAL5016 *
        *                                                              *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available.         *
        ****************************************************************
        The DB2 10 for z/OS ENFM process (job DSNTIJEN) resets the
        SYSUTILX directory table space. If there was any data in
        SYSUTILX for stopped utilities then it will be lost during
        ENFM processing. But the DBET states for the objects involved
        in the stopped utilities will remain. These DBET states will
        cause other utilities running against these objects to abend
        as follows:

            ABND=04E-00C90101,LOC=DSNIDM.DSNIDBMF:5016

        DB2 utility code has been changed so that it will no longer
        ENFM process the SYSUTILX directory table space if there are
1       any stopped utilties. If the ENFM process detects a stopped
        utility then ENFM processing will stop RC=8 and the following
        message will appear in the job output:

        DSNU777I  DSNUECM0 - CATENFM CONVERT STATUS - CONVERT SYSUTILX
                             FAILED - OUTSTANDING OR INCOMPATIBLE
                             UTILITIES
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88781
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUECMI  PM88781
       DSNUECM0  PM88781

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88781   DSNUECMI DSNUECM0

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUECMI
       DSNUECM0

      LISTEND
 UK94512 COVER LETTER END


 UK94519 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM85160 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS users whose queries contain *
        *                 join predicates involving a column           *
        *                 expression or queries joining 3 or more      *
        *                 tables.                                      *
        ****************************************************************
        * PROBLEM DESCRIPTION: DB2 may select an inefficient join      *
        *                      sequence for a query if the query       *
        *                      contains a join predicate involving     *
        *                      a column expression or the query        *
        *                      joins 3 or more tables.                 *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        DB2 may select an inefficient join sequence for a query if the
        query contains a join predicate involving a column expression
        or the query joins 3 or more tables.

        For example,

        SELECT *
          FROM T1, T2, T3
         WHERE T1.C1 = ?
1          AND T1.C2 = T2.C2 + 1 DAY
           AND T2.C3 = T3.C3

        T1 joins T2 by join predicate T1.C2 = T2.C2 + 1 DAY which
        contains an expression. DB2 may select an inefficient join
        sequence for this type of query.


        ADDITIONAL KEYWORDS:

        SQLACCESSPATH  SQLPERFORMANCE
        Code is fixed to solve the problem described as above.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM85160
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM87084:

        See PM87084 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM87084 corrects a problem of incorrect output for a query
        with an ORDER BY clause that refers to a table with an
        OMNIFIND function.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM85160:

        See PM85160 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM85160 corrects a problem of SQL performance when queries
        contain join predicates involving column expressions or
        queries joining 3 or more tables.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM83457:

        A rebind is necessary for static applications to rebuild
        access paths based on the changes in this APAR.

        PM83457 corrects a problem that the DB2 optimizer may select an
        inefficient join sequence for a query if the query has a query
        block with a join of 3 or more tables.

        To make this fix effective for a static application, it must be
1       rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM75197:

        See PM75197 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM75197 corrects a problem of inefficient access path for
        read only queries with FOR UPDATE.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM73214:

        A rebind is necessary for static applications to rebuild
        access paths based on the changes in this APAR.

        PM73214 corrects a problem of inaccurate cost estimation for
        a query when the query contains a view or table expression with
        UNION ALL.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM72676:

        A rebind is necessary for static applications to rebuild
        access paths based on the changes in this APAR.

        PM72676 corrects a problem of inaccurate cost estimation for
        a query when the query contains nested non-correlated
        subqueries.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM58932:

        A rebind is necessary for static applications to rebuild
        access paths based on the changes in this APAR.

        PM58932 corrects a problem that DB2 may choose an inefficient
        join sequence for a query joining 3 or more tables.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
1       affected by this change.
      DB2BIND:
        ***Action for PM34814:

        See PM34814 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM34814 corrects a problem that DB2 may select an inefficient
        join sequence for a query if a declared global temporary table
        is involved or statistics on join columns are not collected.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM32404:

        See PM32404 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM32404 corrects a problem of inaccurate filter factor
        estimation for a predicate that is generated by global
        optimization for an IN subquery or EXISTS subquery if there are
        multiple IN or EXISTS subqueries in the same query block.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM29262:

        See PM29262 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM29262 corrects a problem of inaccurate output in
        DSN_DETCOST_TABLE when a materialized query block occurs.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM25629:

        See PM25629 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM25629 resolves a case in which an inefficient join sequence
        could be chosen for a query block with four or fewer tables.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
1     DB2BIND:
        ***Action for PM17234:

        See PM17234 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM17234 will allow more join permutations to be considered when
        there are a high number of query blocks, but each query block
        contains less than or equal to four tables.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOPKN  PM85160
       DSNXOSJO  PM85160
       DSNXOTS   PM85160

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM85160   DSNXOPKN DSNXOSJO DSNXOTS

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOPKN
       DSNXOSJO
       DSNXOTS

      LISTEND
 UK94519 COVER LETTER END


 UK94558 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM83463 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users *
        *                 of COPY and QUIESCE utilities with OPTIONS   *
        *                 EVENT(ITEMERROR,SKIP) specified.             *
        ****************************************************************
        * PROBLEM DESCRIPTION: When OPTIONS EVENT(ITEMERROR,SKIP) is   *
        *                      specified, COPY and QUIESCE utilities   *
        *                      fail to terminate as expected despite   *
        *                      receiving MSGDSNU183I.                  *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available.         *
        ****************************************************************
        User ran a utility job with syntax similar to the following:

         OPTIONS EVENT(ITEMERROR, SKIP)
         COPY TABLESPACE DSNDB01.SYSUTILX COPYDDN SYSCOPY

        Another utility was running at the same time, so message
        DSNU183I - EXCLUSIVE SYSUTIL UTILITY NOT COMPATIBLE WITH
1                  OTHER ACTIVE UTILITIES
        was correctly issued, which should have caused the COPY job to
        terminate with RC8. But the job continued to do the COPY and
        ended with RC0 instead.

        The problem can also happen with QUIESCE utility.
        Code has been changed so that MSGDSNU183I will cause the utility
        job to terminate properly, even if OPTIONS EVENT (ITEMERROR,
        SKIP) is specified.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM83463
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUGUCC  PM83463

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM83463   DSNUGUCC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUGUCC

      LISTEND
 UK94558 COVER LETTER END


 UK94559 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86559 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of input host      *
        *                 variables with implicit cast in a            *
        *                 distributed environment.                     *
        ****************************************************************
        * PROBLEM DESCRIPTION: An incorrect value is returned when a   *
        *                      little endian small or big integer      *
        *                      input host variable takes part in an    *
        *                      implicit cast operation to a character  *
        *                      data type (e.g. CHAR, VARCHAR, GRAPHIC, *
        *                      VARGRAPHIC, etc.) on a remote server.   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The result (value) returned from an implicit cast can be
        incorrect if and only if the following 3 conditions are true:

          1. The input host variable is defined as a small integer or
             a big integer in little endian format.

          2. The host variable is implicitly cast to a character data
             type (e.g. CHAR, VARCHAR, GRAPHIC, VARGRAPHIC, etc.).

1         3. The implicit cast is executed at the remote server.


        The following example illustrates the problem.

        1. Create a table with a VARCHAR column on a remote server.

           CREATE TABLE T1 (C1 VARCHAR(20));

        2. Write a CLI dynamic application and run it against a remote
           server.

           # make a connection to remote DB2 server

           # define a small integer host variable
           getmem 1 1 SQL_C_SHORT 2
           updatemem 1 sql_c_short value 25

           # bind the small integer host variable as small integer SQL
           # type

           sqlbindparameter 1 1 SQL_PARAM_INPUT SQL_C_SHORT SQL_SMALLINT
           0 0 1
           sqlprepare 1 "INSERT INTO T1(C1) VALUES( ? )" -3
           sqlexecute 1

           sqltransact 1 1 sql_commit

        When the CLI application is passing a small integer value in
        little endian format to a DB2 for z/OS server, and implicit cast
        is used to bind in the value, DB2 does not handle the little
        endian format conversion correctly.  Following the operation,
        the incorrect value can be inserted into C1.  Instead, a numeric
        string of 25 is expected to be inserted into C1.

        Please note.  The incorrect value which can result from the
        conversion of a little endian format could result in an
        unexpected SQLCODE433 (SQLCODE -433) being issued.
        The code in DB2 has been modified to correct the implicit cast
        problem.

        Additional Keywords: DB2INCORR/K INCORROUT SQLINCORR
                             SQLINCORROUT SQLCAST SQLCODE433
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM86559
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXRIHB  PM86559
       DSNXRIHD  PM86559
       DSNXRIHR  PM86559
       DSNXRIHS  PM86559

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1      PM86559   DSNXRIHB DSNXRIHD DSNXRIHR DSNXRIHS

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXRIHB
       DSNXRIHD
       DSNXRIHR
       DSNXRIHS

      LISTEND
 UK94559 COVER LETTER END


 UK94562 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM84540 -
        ****************************************************************
        * USERS AFFECTED: All the users of the IBM                     *
        *                 Text Search for DB2 z/OS.                    *
        ****************************************************************
        * PROBLEM DESCRIPTION: This PTF provides three new index       *
        *                      configuration options for               *
        *                      SYSTS_CREATE,SYSTS_UPDATE  and          *
        *                      SYSTS_ALTER stored procedures:          *
        *                                                              *
        *                      UPDATEAUTOCOMMIT                        *
        *                      COMMITTYPE                              *
        *                      COMMITCYCLES                            *
        *                                                              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        This PTF provides the new index configurations for
        SYSTS_CREATE, SYSTS_UPDATE  and SYSTS_ALTER stored
        procedures: UPDATEAUTOCOMMIT, COMMITTYPE and
        COMMITCYCLES

        Text index update processing already provides a feature to
        specify the commitsize via the UPDATEAUTOCOMMIT argument.
        To provide further control, additional settings are
        available now to determine whether the COMMITTYPE should
        be treated as rows or hours, and how many COMMITCYCLES to
        process.

        An initial update will process data in key order and save
        the last committed key. If the commitcycle is set then
        this key is  used to continue when the update is restarted.
        For an incremental update, after completing the cycles,
        the log entries are deleted, and there is no need a committed
        key to restart processing.

        **************************************************************
        UPDATEAUTOCOMMIT

        Specifies how often a commit operation is performed when
1       fetching documents during an index update. A value of 0
        (zero) means that a commit operation occurs only at the end
        of processing. The default value is 100 and COMMITTYPE is
        ROWS.

        COMMITTYPE

        The value of COMMITTYPE is ROWS or HOURS. If it is ROWS
        then the text index will be committed after the the number
         of rows (value of UPDATEAUTOCOMMIT) is reached. If it is
         HOURS then the text index will be committed after a period
         of time (value of UPDATEAUTOCOMMIT) is reached.
        Default of COMMITTYPE is ROWS.
        This option is always in conjunction with UPDATEAUTOCOMMIT
        or COMMITCYCLES

        COMMITCYCLES

        The numeric value for the number of commit cycles; The
        update of text index will be process for the number of
        commit cycles. By default it is unrestricted cycles, If
        COMMITCYCLES is 0 then the update process will be
        processed as many as need to finish processing.
        COMMITCYCLES always in conjunction with UPDATEAUTOCOMMIT
        and COMMITTYPE.
        ***************************************************************

        1-- Examples of SYSTS_CREATE with new options:
        call sysproc.systs_create('USRT002', 'ITEST',
         'USRT002.TEST(TEXT)',
         'INDEX CONFIGURATION ( UPDATEAUTOCOMMIT 2, COMMITTYPE
        HOURS ,COMMITCYCLES 2)' )

        call sysproc.systs_create('USRT002', 'ITEST',
        'USRT002.TEST(TEXT)',
         'INDEX CONFIGURATION ( UPDATEAUTOCOMMIT 2, COMMITTYPE
        HOURS )' )

        Error cases:
        call sysproc.systs_create('USRT002', 'ITEST',
        'USRT002.TEST(TEXT)',
         'INDEX CONFIGURATION (  COMMITTYPE HOURS ,COMMITCYCLES 2)'
         )

        call sysproc.systs_create('USRT002', 'ITEST',
        'USRT002.TEST(TEXT)',
         'INDEX CONFIGURATION (COMMITCYCLES 2)' )

        2-- Examples of SYSTS_UPDATE with new options:
        call sysproc.systs_update('USRT002', 'ITEST',
        ' INDEX CONFIGURATION ( UPDATEAUTOCOMMIT 2, COMMITTYPE HOURS
        ,COMMITCYCLES 2)')

         call sysproc.systs_update('USRT002', 'ITEST',
        'INDEX CONFIGURATION (UPDATEAUTOCOMMIT 2,COMMITTYPE HOURS )')

1        call sysproc.systs_update('USRT002', 'ITEST',
        ' INDEX CONFIGURATION ( UPDATEAUTOCOMMIT 2000 )')

        Error cases:


         call sysproc.systs_update('USRT002', 'ITEST',
        'INDEX CONFIGURATION ( UPDATEAUTOCOMMIT 2, COMMITCYCLES
        2)')

         call sysproc.systs_update('USRT002', 'ITEST',
        ' INDEX CONFIGURATION (  COMMITTYPE HOURS ,COMMITCYCLES
        2)')

        call sysproc.systs_update('USRT002', 'ITEST',
         ' INDEX CONFIGURATION ( UPDATEAUTOCOMMIT 2, COMMITTYPE
         ,COMMITCYCLES 2)')

         call sysproc.systs_update('USRT002', 'ITEST',
         'INDEX CONFIGURATION ( UPDATEAUTOCOMMIT 2, COMMITTYPE
        HOURS ,COMMITCYCLES )')

        3-- Examples of SYSTS_ALTER with new options:

        CALL SYSPROC.SYSTS_ALTER(  'USRT002', 'INDEX2' ,' UPDATE
        FREQUENCY NONE UPDATE MINIMUM 1 INDEX CONFIGURATION (
        UPDATEAUTOCOMMIT 200, COMMITTYPE ROWS, COMMITCYCLES 4 )'  )

        3-- Examples of SYSTS_ALTER with new options:

        CALL SYSPROC.SYSTS_ALTER(  'USRT002', 'INDEX2' ,' UPDATE
        FREQUENCY NONE UPDATE MINIMUM 1 INDEX CONFIGURATION (
        UPDATEAUTOCOMMIT 200, COMMITTYPE ROWS, COMMITCYCLES 4 )'  )

        CALL SYSPROC.SYSTS_ALTER(  'USRT002', 'INDEX2' ,' UPDATE
        FREQUENCY NONE UPDATE MINIMUM 1 INDEX CONFIGURATION (
        UPDATEAUTOCOMMIT 4, COMMITTYPE HOURS, COMMITCYCLES 2 )'  )

        CALL SYSPROC.SYSTS_ALTER(  'USRT002', 'INDEX2' ,' UPDATE
        FREQUENCY NONE UPDATE MINIMUM 1 INDEX CONFIGURATION (
          UPDATEAUTOCOMMIT 4, COMMITTYPE HOURS )'  )


        CALL SYSPROC.SYSTS_ALTER(  'USRT002', 'INDEX2' ,' UPDATE
        FREQUENCY NONE UPDATE MINIMUM 1 INDEX CONFIGURATION (
        UPDATEAUTOCOMMIT 4, COMMITTYPE HOURS, COMMITCYCLES 2 )'  )

        Error cases:

        CALL SYSPROC.SYSTS_ALTER(  'USRT002', 'INDEX2' ,' UPDATE
        FREQUENCY NONE UPDATE MINIMUM 1 INDEX CONFIGURATION (
        UPDATEAUTOCOMMIT 25, COMMITTYPE HOURS, COMMITCYCLES 2 )'  )

        CALL SYSPROC.SYSTS_ALTER(  'USRT002', 'INDEX2' ,' UPDATE
        FREQUENCY NONE UPDATE MINIMUM 1 INDEX CONFIGURATION (
        UPDATEAUTOCOMMIT 28,  COMMITCYCLES 2 )'  )
1
        CALL SYSPROC.SYSTS_ALTER(  'USRT002', 'INDEX2' ,' UPDATE
        FREQUENCY NONE UPDATE MINIMUM 1 INDEX CONFIGURATION (
        COMMITTYPE HOURS, COMMITCYCLES 2 )'  )

        More detail information of using the new options can be
        found at:

        Administration stored procedures for text search:
        http://pic.dhe.ibm.com/infocenter/dzichelp/v2r2/topic/
        com.ibm.db2z10.doc.srchz/src/tpc/tsrch_storedpro.htm
        The users need to apply this PTF, follow ++HOLD instructions
        before using the new options of the Text Search
        stored procedures.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM84540
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        This PTF provides the new index configuration options
        for SYSTS_CREATE, SYSTS_UPDATE and SYSTS_ALTER
        stored procedures:
        UPDATEAUTOCOMMIT, COMMITTYPE and COMMITCYCLES.

        ***************************************************************
        Actions for customers who are already using DB2 10:
        ***************************************************************
        If you have already installed or migrated to DB2 10 then,
        after applying this PTF, you need to take the following action
        if you use the IBM Text Search for DB2 z/OS:

        Run your copy of job DSNTIJRT with MODE(INSTALL) to add new
        rows to table SYSIBMTS.SYSTEXTSDEFAULTS and to refresh the
        packages for the IBM Text Search.

        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.

        ***************************************************************
        ***************************************************************

        The following information will refer to the "IBM Text Search
        for DB2 for z/OS" book.

        (1) Download the most current version of IBMTS
            ***********************************************************
1           * This action is required for Text Search customers
            ***********************************************************
            Download the most current version which is FIX R1L5.1
            from the following Web site:

        http://www.ibm.com/software/data/db2/zos/downloads/oftss.html

        On this Web site, download the zip file and the readme file
        for IBMTS Text Search for DB2 for z/OS.

        The following shows the names of the zip files
        of IBMTS Text Search Servers:

           Linux32 -  TS_fixR1L5.1_linux32.zip
           Linux64 -  TS_fixR1L5.1_linux64.zip
           Window32 - TS_fixR1L5.1_win32.zip
           Window64 - TS_fixR1L5.1_win64.zip
           zLinux -   TS_fixR1L5.1_zlinux.zip

         For Window32/64: right click the zip then choose extract
          option

          For Linux32/Linux64/zlinux, change mode and unzip the files.
          Example:
                  chmod 755 TS_fixR1L5.1_linux32.zip
                  unzip     TS_fixR1L5.1_linux32.zip

          To install or update the IBMTS server, please refer to
          the following publications:

          --readme.html: document that accompanies the installation
            file.
          --"Installation, Administration, and Reference": the
            product documentation for the IBM Text Search for DB2
            z/OS.

        (2) New IBMTS users: Install the IBMTS server
            ***********************************************************
            * This action is required for Text Search customers
            ***********************************************************
            To install the IBMTS server, the user needs to follow:

            Chapter 4. Installing and configuring text search functions

              --Installing IBM Text Search for DB2 z/OS.

        (3) Existing users: Migrate to IBMTS from OmniFind server
            ***********************************************************
            * This action is required for Text Search customers
            ***********************************************************
            For existing users to migrate IBMTS from OmniFind server
            they need to follow:

          Chapter 4. Installing and configuring text search functions
            --Migrating to IBM Text Search for DB2 for z/OS
              from OmniFind Text Search.
1        or
          --Installing fixes on top of the current server.
            (install IBMTS server on the existing server).


        (4) Where to find more information
        ----------------------------------------------------------------
            The user can look for more information at:

        Installation, Administration, and Reference
        IBM Text Search for DB2 for z/OS:
        http://pic.dhe.ibm.com/infocenter/dzichelp/v2r2/topic/
        com.ibm.db2z10.doc.srchz/src/srchz/dasz_srchz.htm


        Administration stored procedures for text search:
        http://pic.dhe.ibm.com/infocenter/dzichelp/v2r2/topic/
        com.ibm.db2z10.doc.srchz/src/tpc/tsrch_storedpro.htm
      ACTION:
        Please note that the following ACTIONS need to be performed
        with respect to this apar:

        1. Run your copy of job DSNTIJRT with MODE(INSTALL) to
           bind, and grant access to the Text Search stored
           procedures.

        2. Refresh WLM environment defined for Text Search
           stored procedures:
           v wlm,applenv=wlmname,refresh

        3. Refresh DB2 to make sure it will pick up the new
           Text Search modules.
      ACTION:
        ***Action for PM72982 (V10)

        This PTF modifies DB2 installation program DSNTRIN to create the
        LOB table spaces in the DB2 XML Schema Registration (DSNXSR)
        database as LOGGED (by default) rather than NOT LOGGED.  The
        affected table spaces are: SYSXSRA1, SYSXSRA2, SYSXSRA3, and
        SYSXSRA4.  Use of the LOGGED attribute facilitates rollback and
        recovery by ensuring that changes made to the data in these
        table spaces are recorded in the DB2 log.

        This change has no effect on existing instances of these table
        spaces.  If you have already created the DSNXSR database, you
        can alter these table spaces from NOT LOGGED to LOGGED by means
        of the following SQL statements:
          ALTER TABLESPACE DSNXSR.SYSXSRA1 LOGGED;
          ALTER TABLESPACE DSNXSR.SYSXSRA2 LOGGED;
          ALTER TABLESPACE DSNXSR.SYSXSRA3 LOGGED;
          ALTER TABLESPACE DSNXSR.SYSXSRA4 LOGGED;

        Because altering the logging attribute of a table space from
        NOT LOGGED to LOGGED can place the table space in COPY-pending
        status, you might need to copy the table spaces after completing
        this operation.
1   COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSN@O001  PM84540
       DSN@O002  PM84540
       DSN@O004  PM84540
       DSN@O005  PM84540
       DSN@O007  PM84540
       DSN@O008  PM84540
       DSN@O009  PM84540
       DSN@O011  PM84540
       DSN@O012  PM84540
       DSN@O013  PM84540
       DSN@O014  PM84540
       DSN@O015  PM84540
       DSN@O016  PM84540
       DSN@O017  PM84540
       DSN@O019  PM84540
       DSN@O021  PM84540
       DSN@RIN   PM84540
       DSNTESR   PM84540
       DSNTRIN   PM84540
       DSN5OCA3  PM84540
       DSN5OCA6  PM84540
       DSN5OCO3  PM84540
       DSN5OCO6  PM84540
       DSN5OCU3  PM84540
       DSN5OCU6  PM84540
       DSN5OPAL  PM84540
       DSN5OPCR  PM84540
       DSN5OPDR  PM84540
       DSN5OPMS  PM84540
       DSN5OPRE  PM84540
       DSN5OPSD  PM84540
       DSN5OPSP  PM84540
       DSN5OPST  PM84540
       DSN5OPTO  PM84540
       DSN5OPUP  PM84540
       DSN5OTMS  PM84540
       DSN5OTS   PM84540

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM84540   DSN@O001 DSN@O002 DSN@O004 DSN@O005 DSN@O007 DSN@O008
                 DSN@O009 DSN@O011 DSN@O012 DSN@O013 DSN@O014 DSN@O015
                 DSN@O016 DSN@O017 DSN@O019 DSN@O021 DSN@RIN  DSNTESR
                 DSNTRIN  DSN5OCA3 DSN5OCA6 DSN5OCO3 DSN5OCO6 DSN5OCU3
                 DSN5OCU6 DSN5OPAL DSN5OPCR DSN5OPDR DSN5OPMS DSN5OPRE
                 DSN5OPSD DSN5OPSP DSN5OPST DSN5OPTO DSN5OPUP DSN5OTMS
                 DSN5OTS

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNTRIN

      MACROS
       DSN@O001
1      DSN@O002
       DSN@O004
       DSN@O005
       DSN@O007
       DSN@O008
       DSN@O009
       DSN@O011
       DSN@O012
       DSN@O013
       DSN@O014
       DSN@O015
       DSN@O016
       DSN@O017
       DSN@O019
       DSN@O021
       DSN@RIN
       DSNTESR
       DSN5OCA3
       DSN5OCA6
       DSN5OCO3
       DSN5OCO6
       DSN5OCU3
       DSN5OCU6
       DSN5OPAL
       DSN5OPCR
       DSN5OPDR
       DSN5OPMS
       DSN5OPRE
       DSN5OPSD
       DSN5OPSP
       DSN5OPST
       DSN5OPTO
       DSN5OPUP
       DSN5OTMS
       DSN5OTS

      LISTEND
 UK94562 COVER LETTER END


 UK94568 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88799 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 10 for z/OS who have        *
        *                 queries with a LIKE predicate on a           *
        *                 partitioning column defined as CHAR          *
        *                 and use REOPT(ALWAYS)                        *
        ****************************************************************
        * PROBLEM DESCRIPTION: Incorrect output can occur for a query  *
        *                      with a LIKE predicate on a partitioning *
        *                      column defined as CHAR when             *
        *                      REOPT(ALWAYS) is used and page range    *
        *                      screening is chosen                     *
        ****************************************************************
        * RECOMMENDATION:                                              *
1       ****************************************************************
        Incorrect output can occur for a query containing a LIKE
        predicate on a partitioning column defined as CHAR (character
        data type) when REOPT(ALWAYS) is used and page range screening
        is chosen (PAGE_RANGE='Y' in the PLAN_TABLE).  Also, the LIKE
        predicate uses a host variable or parameter marker.  The
        data type of the LIKE pattern string can be mistakenly
        interpreted as CHAR rather than VARCHAR when the column
        is defined as CHAR.  The mismatched data type leads to an
        incorrect translation of the LIKE pattern string, which
        can result in the wrong partitions to be qualified for
        page range screening.

        Additional Keywords:
        INCORROUT SQLINCORROUT SQLINCORR DB2INCORR/K
        PAGERANGE SQLLIKE SQLCHAR SQLREOPT SQLHOSTVAR SQLPMK
        PARAMETERMARKER SQLPMARKER
        Code is changed to correct the data type for interpreting
        LIKE pattern strings in the situation described above, so
        that the correct partitions can be qualified.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88799
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM74543:

        See PM74543 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM74543 corrects a problem of choosing a poorly performing
        access path for a partitioned table when queries involve
        partitioned tables, and EQUAL with host variables or
        parameter markers, and a DPSI (Data Partitioned Secondary
        Index).

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM74152:

        A rebind is necessary for static applications to rebuild
        internal structures used at runtime based on the changes in
        this APAR.

        PM74152 corrects a problem in which DB2 may incorrectly return
        no rows for a query using page range access where a range
        predicate exists on a partitioning column defined as CHAR(1).

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
1     DB2BIND:
        ***Action for PM52548:

        See PM52548 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM52548 fixes an abend 0C4 RC00000038 DSNISPBM + 1A64 that can
        occur during query execution for queries containing IS NULL
        or LIKE predicates.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM38082:

        See PM38082 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM38082 corrects a query performance problem involving
        significant loss of page range screening for queries with
        multi-column partitioning keys and predicates with host
        variables or parameter markers on those columns.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        See PM25059 APAR/PTF text in the PTF cover letter for
        additional information about why a REBIND is necessary.

        PM25059 corrects a problem where the page range reduction
        is done incorrectly.  It may cause DB2 to choose a plan with
        an extra GROUP BY / ORDER BY sort where it is not needed.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOPG1  PM88799
       DSNXOPG2  PM88799

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88799   DSNXOPG1 DSNXOPG2

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOPG1
       DSNXOPG2

      LISTEND
1UK94568 COVER LETTER END


 UK94569 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88066 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of row or column   *
        *                 access control.                              *
        ****************************************************************
        * PROBLEM DESCRIPTION: An unexpected SQLCODE -204 could        *
        *                      be issued or an ABEND04E RC00E70005 in  *
        *                      DSNXGRDS DSNXOACL M900 could occur      *
        *                      when an SQL statement satisfies the     *
        *                      following conditions:                   *
        *                      1. it references a table which is       *
        *                         activated for row or column          *
        *                         access control.                      *
        *                      2. the table qualifier, table name or   *
        *                         table correlation name is a          *
        *                         delimited identifier.                *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        1.The following example could recreate the SQLCODE -204:
        CREATE TABLE "123T1"(C1 CHAR(7), C2 INTEGER) ;
        CREATE PERMISSION RP1 ON "123T1" FOR ROWS WHERE C2 > 20
        ENFORCED FOR ALL ACCESS ENABLE;
        ALTER TABLE "123T1" ACTIVATE ROW ACCESS CONTROL;
        SELECT * FROM "123T1";

        SQLCODE -204 issued when binding the SELECT statement in the
        example.

        2. The following example could recreate the abend:
        CREATE TABLE "123".T1(C1 CHAR(7), C2 INTEGER) ;
        CREATE PERMISSION RP1 ON "123".T1 FOR ROWS WHERE C2 > 20
        ENFORCED FOR ALL ACCESS ENABLE;
        ALTER TABLE "123".T1 ACTIVATE ROW ACCESS CONTROL;
        SELECT * FROM "123".T1;

        The abend could occur when binding above SELECT statement.

        DB2 is updated to handle row or column access control
        correctly to avoid the abend.
        Additional Keywords: SQLPERMISSION SQLMASK SQLCOLUMNMASK
                             SQLCODE204
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88066
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOACL  PM88066

1     CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88066   DSNXOACL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOACL

      LISTEND
 UK94569 COVER LETTER END


 UK94585 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM77517 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of CHECK DATA      *
        *                 utility with PART specified.                 *
        ****************************************************************
        * PROBLEM DESCRIPTION: CHECK DATA PART n against a partitioned *
        *                      table space with LOBs failed with       *
        *                      ABEND0C4 RC00000038 DSNUKREL + x'0C7A'  *
        *                      when the definition of the LOB table    *
        *                      space for partition n is complete but   *
        *                      the definition of the LOB table space   *
        *                      for any of the other partition is not   *
        *                      complete.                               *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available.         *
        ****************************************************************
        User ran a CHECK DATA PART n utility against a partitioned table
        space with LOBs. The CHECK DATA utility failed with ABENDS0C4
        RC38 at DSNUKREL OFFSET0C7A when the definition of the LOB table
        space for partition n was complete but the definition of the LOB
        table space for any of the other partition was not complete. The
        abend happened because CHECK DATA utility was trying to access
        low core storage with a zero pointer to a control block that had
        not been allocated.
        CHECK DATA utility code has been modified to build the control
        block when the definition of the LOB table space for partition
        n is complete.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM77517
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUKINA  PM77517

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM77517   DSNUKINA

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
1      DSNUKINA

      LISTEND
 UK94585 COVER LETTER END


 UK94588 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89622 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of the REPAIR DBD  *
        *                 utility.                                     *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABENDS0C4 DSNUECM0 OFFSET0262 with      *
        *                      REPAIR DBD DIAGNOSE DATABASE.           *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available.         *
        ****************************************************************
        A REPAIR DBD DIAGNOSE DATABASE was done and it abended as
        follows: ABENDS0C4 DSNUECM0 OFFSET0262. Code is shared between
        the REPAIR DBD and CATMAINT utilities. The REPAIR DBD code was
        referencing storage that is only available to the CATMAINT
        utility and this is what caused the problem.
        Code has been modified to correct the aforementioned problem.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89622
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUECM0  PM89622

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89622   DSNUECM0

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUECM0

      LISTEND
 UK94588 COVER LETTER END


 UK94591 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM84025 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of COPY utility    *
        *                 with FULL NO specified.                      *
        ****************************************************************
        * PROBLEM DESCRIPTION: COPY utility with FULL NO specified     *
        *                      created an incremental image copy       *
        *                      following a COPY utility that generated *
        *                      a FlashCopy and sequential copy in the  *
1       *                      same execution. But an incremental      *
        *                      image copy should not have been allowed *
        *                      in that case.                           *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available.         *
        ****************************************************************
        COPY utility with FULL NO specified created an incremental image
        copy when an incremental image copy was not allowed following a
        COPY utility that generated a FlashCopy and sequential copy in
        the same execution. It is because the logic wrongly treated the
        last COPY utility as a normal sequential copy.

        The same issue occurs when COPY utility with FULL NO was run
        after a sequential copy made from a FlashCopy by the COPYTOCOPY
        utility.
        COPY utility with FULL NO specified was modified to issue
        MSGDSNU402I, take a full image copy and return RC4 after
        a COPY utility that generated a FlashCopy and sequential
        copy in the same execution or a sequential image copy that
        was made from FlashCopy.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM84025
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUBAIC  PM84025

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM84025   DSNUBAIC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUBAIC

      LISTEND
 UK94591 COVER LETTER END


 UK94593 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM81305 -
        ****************************************************************
        * USERS AFFECTED: ALL DB2 10 for z/OS users who insert data    *
        *                 on objects defined with COMPRESS YES         *
        ****************************************************************
        * PROBLEM DESCRIPTION: Message DSNT501I followed by ABEND04E   *
        *                      RC00C90108 DSNICMT2 OFFSET393C during   *
        *                      a REFRESH TABLE against a materialized  *
        *                      query table (MQT) which is defined with *
        *                      COMPRESS YES                            *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
1       A REFRESH TABLE statement executed against a materialized query
        table which was defined with COMPRESS YES.  When enough data
        from a fullselect was inserted to start building the compression
        dictionary, a header page was read but not released properly,
        which caused MSGDSNT501I to be issued followed by the ABEND04E
        RC00C90108 at DSNICMT2 +x'393C'.
        The build dictionary routine code was changed to release the
        header page properly
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM81305
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUZLCR  PM81305

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM81305   DSNUZLCR

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUZLCR

      LISTEND
 UK94593 COVER LETTER END


 UK94599 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM83700 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS       *
        *                 users of COPY utility.                       *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABENDS0C4 in DSNUBASI + X'15A8'         *
        *                      following an error condition            *
        *                      in COPY utility.                        *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
          Users running COPY utility may see ABEND0C4 in DSNUBASI
        near OFFSET15A8 and ABEND04E RC00E40347 (subtask abend)
        following a prior error.
          This problem is due to improper error handling logic
        primarily for a subset of less commonly seen errors.
          For example, one known case is triggered by running
        COPY utility on DB2 catalog table space DSNDB06.SYSJAUXB
        after invalidly resetting its underlying data set
        outside of DB2.  In this case, MSGDSNU260I (TABLE SPACE
        IS EMPTY) is issued prior to the ABEND0C4.
          COPY utility code was modified to improve error handling
        logic.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM83700
1   SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUBASI  PM83700

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM83700   DSNUBASI

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUBASI

      LISTEND
 UK94599 COVER LETTER END


 UK94613 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86754 -
        ****************************************************************
        * USERS AFFECTED: All DB2 data sharing users.                  *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C4 RC00000010 in DSNB5RAP         *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Automatic GRECP recovery is started concurrently while DB2
        shutdown is in progress, without proper serialization between
        the two operations, automatic GRECP recovery abended because
        the shutdown operation closes a pageset that is needed by the
        recovery.
        DB2 has been fixed to properly serialize automatic GRECP
        recovery with DB2 shutdown operation.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM86754
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNB1DAA  PM86754

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM86754   DSNB1DAA

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNB1DAA

      LISTEND
 UK94613 COVER LETTER END

1
 UK94635 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM84359 -
        ****************************************************************
        * USERS AFFECTED: All Users of the IBM Data                    *
        *                 Server Driver for JDBC and SQLJ              *
        ****************************************************************
        * PROBLEM DESCRIPTION: IBM Data Sever Driver for JDBC and      *
        *                      SQLJ version 3.65.92 is provided by     *
        *                      this APAR ( JCCV36592 )                 *
        *                                                              *
        *                      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.65) *
        *                      of the IBM Data Server Driver for JDBC  *
        *                      and SQLJ providing an accumulation of   *
        *                      defect fixes and enhancements.          *
        *                                                              *
        *                      Individual items are documented in the  *
        *                      APAR summary section that follows.      *
        ****************************************************************
        * RECOMMENDATION: JCC sub-category keywords:                   *
        *                 JCCCOMMON, JCCT2ZOS, JCCT4, JCCT4XA, JCCSQLJ *
        ****************************************************************
        The following changes are delivered in this APAR:
        _______________________________________________________________
        All connectivity: There were no VARCHAR2 and NUMBER datatypes
        present in DB2. With this fix, driver now maps VARCHAR2 to
        VARCHAR type and NUMBER to DECFLOAT type. (wsdbu00994787)
        _______________________________________________________________
        All connectivity: This feature will improve the performance
        of storing XML data in server by avoiding type conversion.
        With this fix, the binary XML will be stored as binary and XML
        in text format will be stored as TEXT. (wsdbu01049315)
        _______________________________________________________________
        All connectivity: Driver implemented a new API com.ibm.db2.jcc.
        DB2BaseDataSource.setSpecialRegisters(java.util.properties)
        This is a generic API to set values for all special registers.
        e.g.
        Properties pr = new Properties ();
        pr.put ("CURRENT SCHEMA", "'USRT004'");
        ((com.ibm.db2.jcc.DB2BaseDataSource)ds).setSpecialRegisters(pr)
        (wsdbu01050653)
        _______________________________________________________________
        All connectivity: Driver implemented a new way of setting the
        special register values using connection URL.
        e.g.
        "jdbc:db2://XXXXXXXX:XXXXXX/XXXXX:specialRegisters=
        CURRENT_SCHEMA=USRT004;"
        (wsdbu01059558)
1       _______________________________________________________________
        All connectivity: Driver throws SQLCODE4461(-4461) if a
        new line character is embedded in SQL. (wsdbu01052567)
        _______________________________________________________________
        All connectivity: Driver starts supporting the ROUND_HALF_DOWN
        and ROUND_UP modes in Connection.setCurrentRoundingMode API.
        (wsdbu01024529)
        _______________________________________________________________
        All connectivity: The properties db2.jcc.encryptionAlgorithm,
        db2.jcc.securityMechanism, db2.jcc.override.encryptionAlgorithm
        and  db2.jcc.override.securityMechanism are made as global
        properties. (wsdbu01054575)
        _______________________________________________________________
        All connectivity: Improvements in the driver common code to
        reduce CPU impact and enhance performance. (RTC 27371)
        _______________________________________________________________
        Type-2 Connectivity: Driver was flowing the
        SET CURRENT PACKAGESET SQL statement at the end of the
        getConnection processing. In some cases this caused a global
        transaction to be started, leading to unpredictable results
        including SQLCODE913(-913). This issue is fixed in
        setCurrentPackageSet() and setDB2CurrentPackageSet().
        (RTC 28602)
        _______________________________________________________________
        Type-4 Connectivity: Driver parses two single quotes provided
        in a callable statement incorrectly when the target server is
        Db2 for Z/OS. For Z/OS servers, driver needs to do this parsing
        explicitly.(RTC 26291)
        Type-4 connectivity: Driver returns incorrect length, precision
        and scale metadata for TIMESTAMP and TIMESTAMP WITH TIMEZONE
        parameters in a stored procedure. The incorrect parameter
        metadata recorded in a pureQuery capture file causes
        corresponding stored procedure invocations in static mode to
        fail with SQLCODE180(-180). (RTC 27458)
        _______________________________________________________________
        Type-4 Connectivity: Driver throws SQLCODE4474(-4474) while
        setting CURRENTPACKAGEPATH for ZOS trusted connection
        environment. (RTC 27990)
        _______________________________________________________________
        Type-4 Connectivity: Driver starts supporting use of curly
        braces in 'CREATE SECURITY LABEL COMPONENT' SQL statement.
        This statement defines a component that is to be used as part
        of a security policy.e.g  CREATE SECURITY LABEL COMPONENT
        COMPARTMENTS SET {'Collection', 'Research', 'Analysis'}
        (wsdbu01051890)
        _______________________________________________________________
        Type-4 Connectivity: In a workload balancing environment,
        Connection might acquire a specific transport object from the
        pool that was previously used by other thread. In this
        scenario, driver should do a heavy weight reset on that
        transport once but not on subsequent reuse by the same
        connection. Due to multiple reset flows the system
        performance degrades. (RTC 22659)
        _______________________________________________________________
        Type-4 connectivity: The SQLCODE30108(-30108) error message
        has been enhanced. This includes the details of the data
1       sharing member which is failed along with failure-code and
        error-code tokens that indicate the cause of the failure.
        (wsdbu01056765)
        _______________________________________________________________
        Type-4 connectivity: During the first prepare, driver lets
        PreparedStatement.setString() API to set a Special DECFLOAT
        value to a DECIMAL column. For subsequent prepares, it throws
        an "Invalid Conversion exception.". (wsdbu01055876)
        _______________________________________________________________
        Type-4 XA Connectivity: Driver does not close 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. (RTC 28121)
        _______________________________________________________________
        SQLJ All connectivity:  Application encounters the following
        message: "Invalid parameter n: Parameter is not an OUT or INOUT
        parameter.ERRORCODE=-4461, SQLSTATE=42815". This happens when
        callableStatement is executed under WAS with statement
        caching enabled. (RTC 27123 )
        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: PM84359
    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  PM84359
       DSNAQJBB  PM84359
       DSNAQJB1  PM84359
       DSNAQJB2  PM84359
       DSNAQJB3  PM84359
       DSNAQJB4  PM84359
       DSNAQJB5  PM84359
       DSNAQJB6  PM84359
       DSNAQJB7  PM84359
       DSNAQJB8  PM84359
       DSNAQJC1  PM84359
       DSNAQJC2  PM84359
1      DSNAQJC3  PM84359
       DSNAQJC4  PM84359
       DSNAQJRM  PM84359
       DSNAQJS1  PM84359
       DSNAQJS2  PM84359
       DSNAQ3CA  PM84359
       DSNAQ3CC  PM84359
       DSNAQ3CE  PM84359
       DSNAQ3CF  PM84359
       DSNAQ3CM  PM84359
       DSNAQ3C0  PM84359
       DSNAQ3C1  PM84359
       DSNAQ3C2  PM84359
       DSNAQ3C3  PM84359
       DSNAQ3C4  PM84359
       DSNAQ3C5  PM84359
       DSNAQ3C6  PM84359
       DSNAQ3C7  PM84359
       DSNAQ3C8  PM84359
       DSNAQ3C9  PM84359
       DSNAQ3E1  PM84359
       DSNAQ6CC  PM84359
       DSNAQ6CE  PM84359
       DSNAQ6CF  PM84359
       DSNAQ6CM  PM84359
       DSNAQ6C0  PM84359
       DSNAQ6C1  PM84359
       DSNAQ6C2  PM84359
       DSNAQ6C3  PM84359
       DSNAQ6C4  PM84359
       DSNAQ6C5  PM84359
       DSNAQ6C6  PM84359
       DSNAQ6C7  PM84359
       DSNAQ6C9  PM84359

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM84359   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
1      DSNAQ3C3
       DSNAQ3C4
       DSNAQ3C5
       DSNAQ3C6
       DSNAQ3C7
       DSNAQ3C8
       DSNAQ3C9
       DSNAQ6CC
       DSNAQ6CE
       DSNAQ6CF
       DSNAQ6CM
       DSNAQ6C0
       DSNAQ6C1
       DSNAQ6C2
       DSNAQ6C3
       DSNAQ6C4
       DSNAQ6C5
       DSNAQ6C6
       DSNAQ6C7
       DSNAQ6C9

      MACROS
       DSNAQJBA
       DSNAQJBB
       DSNAQJB1
       DSNAQJB2
       DSNAQJB3
       DSNAQJB4
       DSNAQJB5
       DSNAQJB6
       DSNAQJB7
       DSNAQJB8
       DSNAQJC1
       DSNAQJC2
       DSNAQJC3
       DSNAQJC4
       DSNAQJRM
       DSNAQJS1
       DSNAQJS2
       DSNAQ3E1

      LISTEND
 UK94635 COVER LETTER END


 UK94639 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM84363 -
        ****************************************************************
        * USERS AFFECTED: All Users of the IBM Data                    *
        *                 Server Driver for JDBC and SQLJ              *
        ****************************************************************
        * PROBLEM DESCRIPTION: IBM Data Sever Driver for JDBC and      *
        *                      SQLJ version 4.15.94 is provided by     *
        *                      this APAR ( JCCV41594 )                 *
        *                                                              *
1       *                      This APAR is applicable to IBM Data     *
        *                      Sever Driver for JDBC and SQLJ          *
        *                      for DB2 z/OS V11, DB2 z/OS V10 and      *
        *                      DB2 z/OS V9( JCCZOSDB2V11,              *
        *                      JCCZOSDB2V10, JCCZOSDB2V9 )             *
        *                                                              *
        *                      This APAR delivers a new release (4.15) *
        *                      of the IBM Data Server Driver for JDBC  *
        *                      and SQLJ providing an accumulation of   *
        *                      defect fixes and enhancements.          *
        *                                                              *
        *                      Individual items are documented in the  *
        *                      APAR summary section that follows.      *
        ****************************************************************
        * RECOMMENDATION:                                              *
        *                 JCC sub-category keywords:                   *
        *                 JCCCOMMON, JCCT2ZOS, JCCT4, JCCT4XA, JCCSQLJ *
        ****************************************************************
        The following changes are delivered in this APAR:
        _______________________________________________________________
        All connectivity: There were no VARCHAR2 and NUMBER datatypes
        present in DB2. With this fix, driver now maps VARCHAR2 to
        VARCHAR type and NUMBER to DECFLOAT type. (wsdbu00994787)
        _______________________________________________________________
        All connectivity: This feature will improve the performance
        of storing XML data in server by avoiding type conversion.
        With this fix, the binary XML will be stored as binary and XML
        in text format will be stored as TEXT. (wsdbu01049315)
        _______________________________________________________________
        All connectivity: Driver implemented a new API com.ibm.db2.jcc.
        DB2BaseDataSource.setSpecialRegisters(java.util.properties)
        This is a generic API to set values for all special registers.
        e.g.
        Properties pr = new Properties ();
        pr.put ("CURRENT SCHEMA", "'USRT004'");
        ((com.ibm.db2.jcc.DB2BaseDataSource)ds).setSpecialRegisters(pr)
        (wsdbu01050653)
        _______________________________________________________________
        All connectivity: Driver implemented a new way of setting the
        special register values using connection URL.
        e.g.
        "jdbc:db2://XXXXXXXX:XXXXXX/XXXXX:specialRegisters=
        CURRENT_SCHEMA=USRT004;"
        (wsdbu01059558)
        _______________________________________________________________
        All connectivity: Driver throws SQLCODE4461(-4461) if a
        new line character is embedded in SQL. (wsdbu01052567)
        _______________________________________________________________
        All connectivity: Driver starts supporting the ROUND_HALF_DOWN
        and ROUND_UP modes in Connection.setCurrentRoundingMode API.
        (wsdbu01024529)
        _______________________________________________________________
        All connectivity: The properties db2.jcc.encryptionAlgorithm,
        db2.jcc.securityMechanism, db2.jcc.override.encryptionAlgorithm
        and  db2.jcc.override.securityMechanism are made as global
        properties. (wsdbu01054575)
1       _______________________________________________________________
        All connectivity: Improvements in the driver common code to
        reduce CPU impact and enhance performance. (RTC 27371)
        _______________________________________________________________
        Type-2 Connectivity: Driver was flowing the
        SET CURRENT PACKAGESET SQL statement at the end of the
        getConnection processing. In some cases this caused a global
        transaction to be started, leading to unpredictable results
        including SQLCODE913(-913). This issue is fixed in
        setCurrentPackageSet() and setDB2CurrentPackageSet().
        (RTC 28602)
        _______________________________________________________________
        Type-4 Connectivity: Driver parses two single quotes provided
        in a callable statement incorrectly when the target server is
        Db2 for Z/OS. For Z/OS servers, driver needs to do this parsing
        explicitly.(RTC 26291)
        _______________________________________________________________
        Type-4 connectivity: Driver returns incorrect length, precision
        and scale metadata for TIMESTAMP and TIMESTAMP WITH TIMEZONE
        parameters in a stored procedure. The incorrect parameter
        metadata recorded in a pureQuery capture file causes
        corresponding stored procedure invocations in static mode to
        fail with SQLCODE180(-180). (RTC 27458)
        _______________________________________________________________
        Type-4 Connectivity: Driver throws SQLCODE4474(-4474) while
        setting CURRENTPACKAGEPATH for ZOS trusted connection
        environment. (RTC 27990)
        _______________________________________________________________
        Type-4 Connectivity: Driver starts supporting use of curly
        braces in 'CREATE SECURITY LABEL COMPONENT' SQL statement.
        This statement defines a component that is to be used as part
        of a security policy.e.g  CREATE SECURITY LABEL COMPONENT
        COMPARTMENTS SET {'Collection', 'Research', 'Analysis'}
        (wsdbu01051890)
        _______________________________________________________________
        Type-4 Connectivity: In a workload balancing environment,
        Connection might acquire a specific transport object from the
        pool that was previously used by other thread. In this
        scenario, driver should do a heavy weight reset on that
        transport once but not on subsequent reuse by the same
        connection. Due to multiple reset flows the system
        performance degrades. (RTC 22659)
        _______________________________________________________________
        Type-4 connectivity: The SQLCODE30108(-30108) error message
        has been enhanced. This includes the details of the data
        sharing member which is failed along with failure-code and
        error-code tokens that indicate the cause of the failure.
        (wsdbu01056765)
        _______________________________________________________________
        Type-4 connectivity: During the first prepare, driver lets
        PreparedStatement.setString() API to set a Special DECFLOAT
        value to a DECIMAL column. For subsequent prepares, it throws
        an "Invalid Conversion exception.". (wsdbu01055876)
        _______________________________________________________________
        Type-4 XA Connectivity: Driver does not close non-XA
        transaction (with autocommit on) in case of an exception in
1       execution. After the exception, the transaction remains open
        causing the next XA start to fail. (RTC 28121)
        _______________________________________________________________
        SQLJ All connectivity: Application encounters the following
        message: "Invalid parameter n: Parameter is not an OUT or INOUT
        parameter.ERRORCODE=-4461, SQLSTATE=42815". This happens when
        callableStatement is executed under WAS with statement
        caching enabled. (RTC 27123 )
        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: PM84363
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR02 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        ***Action for PM58952

        ____________________________________________________________
        This PTF contains a fix for a defect in the SQLJ translator.
        Incorrect code was generated for an SQL SELECT INTO statement
        using a common table expression specified with the "WITH"
        keyword. To make this fix effective for any impacted SQLJ
        program, after applying the APAR, you must re-translate the
        SQLJ program, then you must run the SQLJ Binder (db2sqljbind)
        again on the affected profiles and rebind the profiles.

        See PM58952 APAR/PTF text in the PTF cover letter for
        further information about this problem. Reference entry
        with (wsdbu01043533) identifier.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNAJJC1  PM84363
       DSNAJJC2  PM84363
       DSNAJ3CC  PM84363
       DSNAJ3CE  PM84363
       DSNAJ3CF  PM84363
       DSNAJ3CM  PM84363
       DSNAJ3C0  PM84363
       DSNAJ3C1  PM84363
       DSNAJ3C2  PM84363
       DSNAJ3C3  PM84363
       DSNAJ3C4  PM84363
       DSNAJ3C5  PM84363
       DSNAJ3C6  PM84363
       DSNAJ3C7  PM84363
       DSNAJ3C9  PM84363
       DSNAJ6CC  PM84363
       DSNAJ6CE  PM84363
       DSNAJ6CF  PM84363
       DSNAJ6CM  PM84363
       DSNAJ6C0  PM84363
       DSNAJ6C1  PM84363
       DSNAJ6C2  PM84363
       DSNAJ6C3  PM84363
1      DSNAJ6C4  PM84363
       DSNAJ6C5  PM84363
       DSNAJ6C6  PM84363
       DSNAJ6C7  PM84363
       DSNAJ6C9  PM84363

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM84363   DSNAJJC1 DSNAJJC2 DSNAJ3CC DSNAJ3CE DSNAJ3CF DSNAJ3CM
                 DSNAJ3C0 DSNAJ3C1 DSNAJ3C2 DSNAJ3C3 DSNAJ3C4 DSNAJ3C5
                 DSNAJ3C6 DSNAJ3C7 DSNAJ3C9 DSNAJ6CC DSNAJ6CE DSNAJ6CF
                 DSNAJ6CM DSNAJ6C0 DSNAJ6C1 DSNAJ6C2 DSNAJ6C3 DSNAJ6C4
                 DSNAJ6C5 DSNAJ6C6 DSNAJ6C7 DSNAJ6C9

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNAJ3CC
       DSNAJ3CE
       DSNAJ3CF
       DSNAJ3CM
       DSNAJ3C0
       DSNAJ3C1
       DSNAJ3C2
       DSNAJ3C3
       DSNAJ3C4
       DSNAJ3C5
       DSNAJ3C6
       DSNAJ3C7
       DSNAJ3C9
       DSNAJ6CC
       DSNAJ6CE
       DSNAJ6CF
       DSNAJ6CM
       DSNAJ6C0
       DSNAJ6C1
       DSNAJ6C2
       DSNAJ6C3
       DSNAJ6C4
       DSNAJ6C5
       DSNAJ6C6
       DSNAJ6C7
       DSNAJ6C9

      MACROS
       DSNAJJC1
       DSNAJJC2

      LISTEND
 UK94639 COVER LETTER END


 UK94648 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM85052 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 9 and 10 for z/OS.          *
1       ****************************************************************
        * PROBLEM DESCRIPTION: An ABEND04E RC00E50097 may occur in     *
        *                      CSECT DSNB5RAP after an agent is        *
        *                      cancelled during agent allocation       *
        *                      while suspended in buffer manager.      *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        If an agent is cancelled during allocation while suspended
        in buffer manager and does not drive a Unit of Recovery,
        recovery actions for buffer manager do not resume the
        suspended agent correctly.
        Agent deallocation has been modified to drive buffer manager
        clean up if the agent was active in buffer manager when it was
        cancelled.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM85052
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNTADL   PM85052

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM85052   DSNTADL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNTADL

      LISTEND
 UK94648 COVER LETTER END


 UK94651 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88433 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of pre-  *
        *                 v8 bound plans/packages that contain special *
        *                 registers without long name support when an  *
        *                 IFCID341 trace is active.                    *
        ****************************************************************
        * PROBLEM DESCRIPTION: An ABEND04E RC00E70005 at DSNXVTRS M420 *
        *                      on DB2 v9 can occur when a pre-v8 bound *
        *                      plan/package is running that contains a *
        *                      special register LOCATION value when an *
        *                      IFCID341 trace is active.               *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An ABEND04E RC00E70005 at DSNXVTRS M420 on DB2 v9 can occur when
        executing a pre-v8 bound plan/package that incorrectly
        references a special register value (for COLLECTION id) when
1       processing a local location name (i.e. for a CONNECT statement)
        if an IFCID341 trace is active.

        The failure occurs because DB2 uses an improper length value
        (zero) which is associated with a COLLECTION ID (bind option) or
        the SET CURRENT PACKAGESET special register when processing the
        local location name for an IFCID341 trace.  Instead, the length
        of the local location name should be used.

        Please note that a similar failure can occur when running the
        same plan/package on DB2 10 for z/OS.

        The code in DB2 is modified to use the length of the local
        location name value instead of the collection identifier
        length for pre-v8 plans/packages which will prevent the
        abend.

        Additional Keywords: IFCID341 SQLSPECIALREG SQLLOCAL SQLCONNECT
                             SQLMIGRATION
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88433
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXEBR9  PM88433

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88433   DSNXEBR9

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXEBR9

      LISTEND
 UK94651 COVER LETTER END


 UK94661 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88765 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users using indexes      *
        *                 created on varying length graphic columns    *
        *                 (VARGRAPHIC)                                 *
        ****************************************************************
        * PROBLEM DESCRIPTION: SQLINCORROUT occurred for query using   *
        *                      index access path with index defined on *
        *                      varying length graphic columns          *
        *                      (VARGRAPHIC)                            *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        SQLINCORROUT occurred for query using index access path with
1       index defined on varying length graphic columns (VARGRAPHIC).
        Key comparison routine failed to compare remainder of key with
        the padding character(s). An incorrect displacement was used
        causing the key to be rejected from the result set.


        Following are two examples that produce incorrect results:
        PADDED INDEX:
             CREATE TABLE T1 (C1 VARGRAPHIC(255) NOT NULL,
                              C2 CHAR(10) WITH DEFAULT NULL)
                          CCSID UNICODE;
             CREATE INDEX IX1 ON T1 (C2,C1) PADDED;
             INSERT INTO T1 (C1) VALUES ('DB2');
             COMMIT;

             SELECT COUNT(*) FROM T1 WHERE C1 = 'DB2';
             -- expect value of 1.


        NOT PADDED INDEX:
             CREATE TABLE T1 (C1 VARGRAPHIC(255) NOT NULL,
                              C2 CHAR(10) WITH DEFAULT NULL)
                          CCSID UNICODE;
             CREATE INDEX IX1 ON T1 (C2,C1) NOT PADDED;
             INSERT INTO T1 (C1) VALUES ('DB2'||REPEAT(' ', 200));
             COMMIT;

             SELECT COUNT(*) FROM T1 WHERE C1 = 'DB2';
             -- expect value of 1.



        Additional Keywords:
             SQLINCORR SQLINCORROUT INCORROUT DB2INCORR/K SQLINDEX
        DB2 has been modified to correctly compare varying length
        graphic keys with padding character(s).
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88765
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNKFNCS  PM88765

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88765   DSNKFNCS

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNKFNCS

      LISTEND
 UK94661 COVER LETTER END

1
 UK94683 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM81419 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9, 10 for z/OS users of XML.         *
        ****************************************************************
        * PROBLEM DESCRIPTION: SQLCODE -904 may be issued without any  *
        *                      reason code and resource type during    *
        *                      parsing or validation of XML data.      *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        DB2 calls z/OS XMLSS for XML parsing and validation. When the
        z/OS XMLSS function calls end abnormally(e.g. abend), DB2
        may issue SQLCODE -904 without any reason code and resource
        type.
        DB2 is modified to issue SQLCODE -20101 with new reason code
        token instead of issuing SQLCODE -904.

        Additional keywords: SQLXML XMLALL XMLSCHEMA SQLCODE904
                             SQLCODE20101
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM81419
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DOCUMENTATION:
        PM81419 introduces the following changes to externals:

        DB2 calls z/OS XMLSS for XML parsing  and validation. When the
        z/OS XMLSS function calls end abnormally(e.g. abend),
        DB2 is modified to issue SQLCODE -20101 with new reason code
        token instead of issuing SQLCODE -904.

        Five new reason codes are added to SQLCODE -20101.
        -20101
        THE FUNCTION function-name FAILED WITH REASON reason-code

        reason-code
        00D50006
        The z/OS XMLSS function, GXL4INI  call ended abnormally.
        This reason code may also be issued when the XMLPARSE or
        DSN_XMLVALIDATE functions are implicitly invoked.

        00D50007
        The z/OS XMLSS function, GXL4CTL  call ended abnormally.
        This reason code may also be issued when the XMLPARSE or
        DSN_XMLVALIDATE functions are implicitly invoked.

        00D50008
        The z/OS XMLSS function, GXL4PRS call ended abnormally.
        This reason code may also be issued when the XMLPARSE or
        DSN_XMLVALIDATE functions are implicitly invoked.

        00D50009
1       The z/OS XMLSS function, GXL4QXD  call ended abnormally.
        This reason code may also be issued when the XMLPARSE or
        DSN_XMLVALIDATE functions are implicitly invoked.

        00D5000A
        The z/OS XMLSS function, GXL4TRM  call ended abnormally.
        This reason code may also be issued when the XMLPARSE or
        DSN_XMLVALIDATE functions are implicitly invoked.

        Programmer response
        00D50006  to 00D5000A
        If you determine that your application is not the
        source of the error, contact IBM Software Support.

        Information about this changed message will be included in the
        Information Management Software for z/OS Solutions Information
        Center (http://publib.boulder.ibm.com/infocenter/imzic) at a
        later date.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNNOBXV  PM81419
       DSNNOPAR  PM81419
       DSNNOPVP  PM81419

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM81419   DSNNOBXV DSNNOPAR DSNNOPVP

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNNOBXV
       DSNNOPAR
       DSNNOPVP

      LISTEND
 UK94683 COVER LETTER END


 UK94695 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM84536 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 and 10 for z/OS users of SQL       *
        *                 statement containing multiple set operators  *
        *                 (SETOPs).                                    *
        ****************************************************************
        * 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 SETOPs;     *
        *                      2. another table expression or VIEW     *
        *                         referenced in VW#1 is also defined   *
        *                         with multiple SETOPs.                *
        ****************************************************************
1       * 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.
        DB2 has been modified correctly to handle the ABEND in
        aformentioned SQL statement.

        Keyword: SQLUNION SQLUNIONALL SQLVIEW SQLTABLEEXPR
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM84536
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM84536:

        See PM84536 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM84536 corrects a problem of ABEND04E RC00E72018 at location
        DSNXGRDS.DSNXSINE: 1342 when an SQL statement satisfies all of
        the following conditions:
        1. a table expression or VIEW (VW#1) is defined with multiple
           SETOPs;
        2. another table expression or VIEW referenced in VW#1 is also
           defined with multiple SETOPs.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
1       affected by this change.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXODSO  PM84536

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM84536   DSNXODSO

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXODSO

      LISTEND
 UK94695 COVER LETTER END


 UK94697 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86838 -
        ****************************************************************
        * USERS AFFECTED: All LOB table space of DB2 for z/OS V10      *
        *                 with GBPCHCHE SYSTEM                         *
        ****************************************************************
        * PROBLEM DESCRIPTION: Various 00C90101 abends may occur       *
        *                      on a LOB table space running under      *
        *                      Data Sharing using GBPCAHE SYSTEM.      *
        *                      Possible abends are:                    *
        *                                                              *
        *                      RC00C90101 DSNODAL1:5003                *
        *                      RC00C90101 DSNOALLO:5022                *
        *                      RC00C90101 DSNODEAL:501C                *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When inserting LOB data bigger than 2M in size, DB2 may
        determine to process the entire data with a smaller subset of
        it. In this situation, the LOB map page is being updated
        several time until the entire LOB data is inserted.
        The LOB map page should be always processed as a non-system
        page, but repeated updates against the same LOB map
        page, could result in it being processed as either a system
        page or non-system when GBPCACHE is set to SYSTEM.
        Therefore, the final LOB map page written to DASD could be
        down level. As a result, the query UR that selects this
        LOB object after it has been inserted, could possibly get a
        down level LOB map page and thus cause data corruption.
        DB2 code is modified to ensure a LOB map page is always
        processed as a non-system page.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM86838
    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      DSNOFLMP  PM86838

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM86838   DSNOFLMP

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNOFLMP

      LISTEND
 UK94697 COVER LETTER END


 UK94713 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM74267 -
        ****************************************************************
        * USERS AFFECTED: All Users of DB2                             *
        ****************************************************************
        * PROBLEM DESCRIPTION: ENABLE FAST LOG APPLY IN ALL CASES      *
        *                      DURING DB2 RESTART.                     *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Today, Fast Log Apply (FLA) is not always enable during DB2
        restart. This is because, unlike, DB2 main-line data recovery
        which enables FLA based on either external ZPARM (DB2 V9)
        setting or internal zparm setting (DB2 V10), restart is using
        work load manager token to enable FLA function. However, the
        work load manager connection token (ASCECTKN) being used is
        always zero since the connection token was not calculated
        correctly. The Data Manager restart logic is changed so that the
        determination of enabling FLA will not depend on work load
        manager being initialized. FLA will be always active during
        restart. This should help improve the over all performance of
        DB2 restart.
        DB2 restart logic is changed so that it will always used FLA
        during the forward log recovery phase.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM74267
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNIARPL  PM74267
       DSNIECUR  PM74267
       DSNIFLAA  PM74267
       DSNIFLAR  PM74267
       DSNILHIS  PM74267
       DSNILOGA  PM74267

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM74267   DSNIARPL DSNIECUR DSNIFLAA DSNIFLAR DSNILHIS DSNILOGA

1     THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIARPL
       DSNIECUR
       DSNIFLAA
       DSNIFLAR
       DSNILHIS
       DSNILOGA

      LISTEND
 UK94713 COVER LETTER END


 UK94727 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88530 -
        ****************************************************************
        * USERS AFFECTED: All DB2 V10 users that have completed ENFM   *
        *                 step ENFM0037.                               *
        ****************************************************************
        * PROBLEM DESCRIPTION: Message DSNI031I indicating lock        *
        *                      escalation on DSNDB01.DBD01 and message *
        *                      DSNT375I indicating a deadlock are      *
        *                      received on the console.                *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An application was deleting and creating many DBD objects for
        example tables and indexes.  After a period of time MSGDSNI031I
        indicating lock escalation and message MSGDSNT375I indicating a
        deadlock are seen.
        System parameters and the workload on the system determine when
        lock escalation can occur. When escalation happens the system
        automatically upgrades the lock from row level to page or
        table space which could cause the deadlock.

        DSNDB01.DBD01 is a system object and lock escalation should have
        been disabled.  The internal definition of DSNDB01.DBD01 has
        been updated to prevent lock escalation and the deadlock.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88530
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNGEDB1  PM88530

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88530   DSNGEDB1

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNGEDB1
1
      LISTEND
 UK94727 COVER LETTER END


 UK94729 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM85433 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 and 10 for z/OS users of XML       *
        *                 publishing function.                         *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C4 LOC=DSNNXML.DSNNOSCO+C2A2 and  *
        *                      DB2 termination may occur when the XML  *
        *                      publishing function is processing a     *
        *                      zero length LOB data.                   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        ABEND0C4 LOC=DSNNXML.DSNNOSCO+C2A2 and DB2 termination may
        occur when the XML publishing function is processing a zero
        length LOB data.

        For example:
          Following statements will create two tables, T1 and T2.

            CREATE TABLE T1 (C1 CHAR(10));
            CREATE TABLE T2 (X1 XML);

          Following INSERT statements insert some data into the tables.

            INSERT INTO T1 VALUES('DATA1');
            INSERT INTO T1 VALUES('DATA2');

            INSERT INTO T2 VALUES 
('<a><b>3</b><b>5</b></a>');
 

          In the following query, the XMLSERIALIZE function will return
          zero length LOB data.

            SELECT
              XMLDOCUMENT(
                XMLELEMENT(NAME "E1",
                  XMLELEMENT(NAME "E2", STRIP(T1.C1)),
                  XMLSERIALIZE(
                    XMLQUERY('$doc/x' PASSING T2.X1 AS "doc") AS 
CLOB)
 
                )
              )
            FROM T1, T2;

          When DB2 is processing the query, the ABEND0C4 LOC=DSNNXML.
          DSNNOSCO+C2A2 and DB2 termination may occur.
        DB2 is modified to process the zero length LOB data correctly.

        Additional keywords: SQLXML XMLALL
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM85433
1   SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNNOBSC  PM85433
       DSNNOCCN  PM85433
       DSNNOSCO  PM85433

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM85433   DSNNOBSC DSNNOCCN DSNNOSCO

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNNOBSC
       DSNNOCCN
       DSNNOSCO

      LISTEND
 UK94729 COVER LETTER END


 UK94763 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86530 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of CHECK DATA with *
        *                 INCLUDE XML TABLESPACES option.              *
        ****************************************************************
        * PROBLEM DESCRIPTION: A CHECK DATA INCLUDE XML TABLESPACES    *
        *                      ALL abended with ABEND04E RC00E40005 at *
        *                      DSNUKXSR + x'0C36' along with           *
        *                      MSGICE122A or MSGICE006A because of     *
        *                      invalid FILSZ or AVGRLEN passed to      *
        *                      DFSORT.                                 *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available.         *
        ****************************************************************
        A CHECK DATA INCLUDE XML TABLESPACES ALL ran on a partitioned
        table space which had two associated XML table spaces.  The job
        failed with ABEND04E RC00E40005 at DSNUKXSR OFFSET0C36, along
        with the message ICE122A - C FILSZ VALUE INVALID or ICE006A -
        C OPERAND DEFINER ERROR, because invalid FILSZ or AVGRLEN was
        passed to DFSORT.
        The problem occurred because negative real-time statistics (RTS)
        values were used to estimate the record count and the average
        row length for the XML data.

        Additional Keywords: RC00E40347, MSGDSNU3343I, DSNU3343I
        CHECK DATA code has been modified to not use a negative DATASIZE
        value from RTS.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM86530
    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
       DSNUKXCH  PM86530

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM86530   DSNUKXCH

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUKXCH

      LISTEND
 UK94763 COVER LETTER END


 UK94764 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88943 -
        ****************************************************************
        * USERS AFFECTED: Users of external SQL procedures on DB2      *
        *                 10 for z/OS.                                 *
        ****************************************************************
        * PROBLEM DESCRIPTION: When warning message DSNH401I is issued *
        *                      in DB2 module DSNHSMS2 for the          *
        *                      preparation of an external SQL          *
        *                      procedure, DB2 may not create the       *
        *                      external SQL procedure successfully     *
        *                      and DB2 may issue SQLCODE -440          *
        *                      incorrectly.                            *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When DB2 issues DSNH401I warning message for an external SQL
        procedure with incompatible operands for a comparison operator,
        DB2 may not create the external SQL procedure successfully and
        it may issue SQLCODE -440 incorrectly.

        Additional keywords: SQLCODE440 MSGDSNH401I SQLEXTERNALSQLPL
        DB2 code is corrected so that DB2 will create the external SQL
        procedure successfully even when the warning message DSNH401I
        is issued.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88943
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNHSMS2  PM88943

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88943   DSNHSMS2

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1
      MODULES
       DSNHSMS2

      LISTEND
 UK94764 COVER LETTER END


 UK94765 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM83933 -
        ****************************************************************
        * USERS AFFECTED: DB2 10 for z/OS users of ALTER TABLE         *
        *                 ALTER COLUMN SET DATA TYPE when the data     *
        *                 type of the specified column is TIMESTAMP    *
        *                 and the column is part of the partitioning   *
        *                 key.                                         *
        ****************************************************************
        * PROBLEM DESCRIPTION: SYSIBM.SYSINDEXPART field, LIMITKEY,    *
        *                      may contain incorrect values as a       *
        *                      result of a TIMESTAMP column alter-     *
        *                      ation.                                  *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The internal limit key value may be stored incorrectly as a
        result of a TIMESTAMP column alteration when the column is
        part of the partitioning key. The internal limit key value
        is stored in SYSINDEXPART.LIMITKEY for index-controlled
        partitioning and SYSTABLEPART.LIMITKEY_INTERNAL for
        table-controlled partitioning.

        This may result in limit keys that are out of order, or if
        the partitioning key consists of only TIMESTAMP columns which
        have been altered, then all partitions wil have the same
        incorrect limit key values.

        Incorrect output, data loss, or other unexpected results
        may occur on subsequent operations on the table. For example,
        SELECT may fail to retrieve all rows. DELETE, and UPDATE may
        fail to find rows to delete or update respectively.
        Additionally, data loss may occur when REORG is run while the
        limit key values are incorrect if there is data that is
        greater than the last partitioning key.
        DB2 has been modified to correctly update SYSINDEXPART.LIMITKEY
        and SYSTABLEPART.LIMITKEY_INTERNAL when altering a TIMESTAMP
        column that is part of the limit key.

        This apar does not fix existing incorrect SYSINDEXPART.LIMITKEY
        or SYSTABLEPART.LIMITKEY_INTERNAL values. Additionally, this
        does not restore lost data. To fix affected tables, alter the
        limit keys to the desired values followed by REORG.

        ADDITIONAL KEYWORDS:
        SQLALTER
        DB2INCORR/K
1       INCORROUT
        SQLINCORR
        SQLINCORROUT
        SQLTIMESTAMP
        SQLALTER
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM83933
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXISB5  PM83933

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM83933   DSNXISB5

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXISB5

      LISTEND
 UK94765 COVER LETTER END


 UK94766 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86374 -
        ****************************************************************
        * USERS AFFECTED: All Distributed Data Facility (DDF) users    *
        *                 accessing DB2 10 for z/OS in new function    *
        *                 mode from a non-Java IBM Data Server Client  *
        *                 Driver where the client application has      *
        *                 input host variables that undergo implicit   *
        *                 casting.                                     *
        ****************************************************************
        * PROBLEM DESCRIPTION: A client application using a non-Java   *
        *                      IBM Data Server Driver accesses a DB2   *
        *                      10 for z/OS server in New Function Mode *
        *                      (NFM), passing in a character input     *
        *                      value that is an empty string or        *
        *                      contains all blank characters where the *
        *                      target has a numeric SQL type.  The     *
        *                      statement correctly fails with SQLCODE  *
        *                      -420, due to the invalid character      *
        *                      value, which cannot be implicitly cast  *
        *                      to a numeric target.  However, this     *
        *                      application successfully executed when  *
        *                      accessing a DB2 server at version 9 and *
        *                      below or when accessing DB2 10          *
        *                      Conversion Mode (CM).                   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The remote statement being processed by DB2 contains invalid
1       character data that cannot be implicitly cast.  The statement
        executed correctly against DB2 9 and below and against DB2 10
        CM because those levels do not provide implicit cast support.
        As a result, the input data was correctly flagged as being in
        error and the statement failed with SQLCODE -301.  The non-Java
        IBM Data Server Client driver provides a property called
        RetryOnError that allows for the statement to be retried with
        corrected user data when SQLCODE -301 is received.  The client
        driver corrects the invalid character data, converting to a
        numeric, before sending to DB2.  With implicit cast support in
        DB2 10 NFM, this corrective action is not being performed by
        the client driver since the statement fails with SQLCODE -420
        instead.  The client driver does not have support to redrive
        the statement for SQLCODE -420.
        .
        One solution is for the application to correct the invalid
        inputs.
        .
        Another solution is provided by the IBM Data Server Driver.
        See APAR IC92430.  Refer to the APAR for details.
        To help customers determine whether they have applications that
        may fail with the same error as described above, the DB2 10 for
        z/OS server is providing new trace support and a new option for
        the DDF_COMPATIBILITY ZPARM.  The trace support allows you to
        detect applications that may encounter the same failures as
        described above.  The ZPARM allows you to disable implicit
        casting for such application running in V10 NFM while you
        implement corrective actions either through changes to your
        application or through the use of client driver support.

        If you are currently in V10 Conversion Mode (CM), with this PTF,
        you can enable the trace to identify applications that may have
        the same problem as described here after migration to New
        Function Mode (NFM).

        If you are currently in V10 NFM or are moving to V10 NFM, with
        this new ZPARM option, you can restore the server bind-in
        processing behavior without implicit cast.  If the ZPARM option
        to disable implicit cast is specified, you can continue to use
        the trace to monitor and identify applications that may be
        problematic, as described above.

        If you have an application with a statement that fails with
        SQLCODE -420 in DB2 10 NFM due to invalid character input data
        that cannot be implicitly cast to numeric targets, then if you
        specify the new DDF_COMPATIBILITY ZPARM option, as described
        below, that statement will now successfully execute as it did
        when it was executed against DB2 version 9 and below or against
        DB2 10 CM.

        The ZPARM and trace details:

        1. This PTF adds a new option, DISABLE_IMPCAST_NJV, to the DB2
        subsystem parameter DSN6FAC.DDF_COMPATIBILITY.  You can use the
        DDF_COMPATIBILITY parameter to enable DB2 10 DDF compatibility
        with older client drivers.  The new DDF_COMPATIBILITY option is:
1
        - DISABLE_IMPCAST_NJV: Use the pre-V10 server
                        compatibility behavior which is
                        not to implicitly cast input host
                        variables during server host
                        variable bind-in processing.
                        This option provides such
                        compatibility only for non-Java IBM
                        Data Server drivers at or below
                        Version 10.5.  It is ignored for
                        any non-Java IBM Data Server driver
                        at any higher level.

                        This option is deprecated in DB2 10.

        If the DISABLE_IMPCAST_NJV option is specified on any member of
        a data sharing environment, it is recommended to specify it on
        all members.

        DDF_COMPATIBILITY options can be specified individually or
        together.  Examples:
          DDF_COMPATIBILITY=
          DDF_COMPATIBILITY=DISABLE_IMPCAST_NJV
          DDF_COMPATIBILITY=SP_PARMS_NJV
          DDF_COMPATIBILITY=(SP_PARMS_NJV,DISABLE_IMPCAST_NJV)

        The default for DDF_COMPATIBILITY remains null (as shown in
        the first example above) meaning that DB2 10 DDF behavior is
        maintained with all clients.

        2.  The PTF also provides a way to detect when SQLCODE -301 is
        generated for incompatible data type conversions occurring
        during server host variable bind in when the client application
        is using a non-Java IBM Data Server Driver and implicit cast is
        not in effect.

        When IFCID 0366 is enabled on DB2 10 for z/OS server when
        implicit casting is not in effect, and when the application is
        using a non-Java IBM Data Server Driver at or below version
        10.5, then DB2 10 server will produce the IFCID 0366 trace
        records indicating, by the following new value in the QW0366FN
        field, when SQLCODE -301 error for incompatible data type
        conversion during host variable bind is raised.

        QW0366FN = 7

          A QW0366FN 7 record indicates that DB2 for z/OS server issued
          a SQLCODE -301 for incompatible data type conversion from
          string data type (e.g. CHAR, VARCHAR, GRAPHIC, VARGRAPHIC
          etc.) to numeric data type in V10 CM if implicit cast is not
          supported or if the server is in V10 NFM when the
          DDF_COMPATIBILITY ZPARM is set to DISABLE_IMPCAST_NJV
          or SP_PARMS_NJV to disable implicit cast, and the client is
          as specified above.

        When examining IFCID 0366 trace records collected, an
1       application programmer who finds any records with a QW0366FN
        value of 7 can take a close look at the input string which is
        converted to a numeric data and make sure it does not contain
        any invalid numeric character string (e.g. string with all
        blank, or empty string with length 0 etc.).  Once the
        application is free of those invalid numeric character string,
        DB2 can convert them into a numeric target data when implicit
        cast feature is enabled.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM86374
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM86374 (DB2 10)

        This PTF adds a new option, DISABLE_IMPCAST_NJV, to the DB2
        subsystem parameter DSN6FAC.DDF_COMPATIBILITY.  You can use the
        DDF_COMPATIBILITY parameter to enable DB2 10 DDF compatibility
        with older client drivers.  The new DDF_COMPATIBILITY option is:

        - DISABLE_IMPCAST_NJV: Use the pre-V10 server
                        compatibility behavior which is
                        not to implicitly cast input host
                        variables during server host
                        variable bind-in processing.

                        This option provides such
                        compatibility only for non-Java IBM
                        Data Server drivers at or below
                        Version 10.5.  It is ignored for
                        any non-Java IBM Data Server driver
                        at any higher level.

                        This option is deprecated in DB2 10.

        If the DISABLE_IMPCAST_NJV option is specified on any member of
        a data sharing environment, it is recommended to specify it on
        all members.

        DDF_COMPATIBILITY options can be specified individually or
        together.  Examples:
          DDF_COMPATIBILITY=
          DDF_COMPATIBILITY=DISABLE_IMPCAST_NJV
          DDF_COMPATIBILITY=SP_PARMS_NJV
          DDF_COMPATIBILITY=(SP_PARMS_NJV,DISABLE_IMPCAST_NJV)

        The default for DDF_COMPATIBILITY remains null (as shown in
        the first example above) meaning that DB2 10 DDF behavior is
        maintained with all clients.

        If you have already installed or migrated to this version of DB2
        you need to take the following actions after applying this PTF:
        (1) Update customized copies of DB2 installation CLIST members
        (2) Update your customized copy of job DSNTIJUZ
        (3) Update private copies of the DSNTIDxx CLIST input member
1
        Detailed guidance for these actions follows:
        ----------------------------------------------------------------
        (1) Update customized copies of DB2 installation CLIST members
        ----------------------------------------------------------------
        ==> This action is recommended for all customers

            This PTF modifies CLIST member DSNTINST in the SDSNCLST
            target library only. You need to redo any record format
            changes and reapply any tailoring you have done to your
            copies of this CLIST. You may also want to move it to the
            prefix.NEW.SDSNCLST data set, where the CLISTs processed by
            job DSNTIJVC reside.
        ----------------------------------------------------------------
        (2) Update your customized copy of job DSNTIJUZ
        ----------------------------------------------------------------
        ==> This action is required for all customers who want to use
            the DISABLE_IMPCAST_NJV option of the DDF_COMPATIBILITY
            parameter, with or without the SP_PARMS_NJV option

            After applying this PTF, edit your customized copy of
            job DSNTIJUZ as follows:
            * Add or update the DDF_COMPATIBILITY keyword parameter in
              one of the following formats:
                DDF_COMPATIBILITY=DISABLE_IMPCAST_NJV,
                DDF_COMPATIBILITY=(SP_PARMS_NJV,DISABLE_IMPCAST_NJV),
              to the invocation of the DSN6FAC macro.  Make sure to add
              a continuation character in column 72 if needed.  If you
              omit adding DDF_COMPATIBILITY here, the value will be set
              to the default of null when you assemble the DSNZPxxx
              module.
            * Run the first two steps of the DSNTIJUZ job you modified.
            * After the job completes, you must either use the -SET
              SYSPARM command or stop and restart DB2 for the change to
              take effect.
        ----------------------------------------------------------------
        (3) Update private copies of the DSNTIDxx CLIST input member
        ----------------------------------------------------------------
        ==> This action is required for all customers

             This PTF modifies the entry for DDF_COMPATIBILITY in the
             CLIST default input members in the SDSNSAMP target library.
             You need to add or update this entry in all private copies
             of your CLIST output DSNTIDxx member. In each such copy,
             convert any existing DDF_COMPATIBILITY entry in this format

               DDF_COMPATIBILITY CHARR M  NONE        NONE          <x>

             to the format below.  If no entry for DDF_COMPATIBILITY is
             present, add one that is in the format below.

               DDF_COMPATIBILITY STR   M  <x>

             Change <x> to NULL if you skipped step (2), above.
             Otherwise, change <x> to one of the following:
               SP_PARMS_NJV,
1              DISABLE_IMPCAST_NJV
               SP_PARMS_NJV,DISABLE_IMPCAST_NJV

             If you do not add DDF_COMPATIBILITY to a DSNTIDxx
             member, the DB2 installation CLIST will assume
             'DDF_COMPATIBILITY=,' when run with that member as input.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSN@XAZP  PM86374
       DSNDQWPZ  PM86374
       DSNDQW05  PM86374
       DSNLXRSS  PM86374
       DSNTIDXA  PM86374
       DSNTIDXB  PM86374
       DSNTINST  PM86374
       DSNTXAZP  PM86374
       DSNWZIFA  PM86374
       DSNXRIHB  PM86374
       DSNXRIHD  PM86374
       DSNXRIHR  PM86374
       DSNXRIHS  PM86374
       DSN6FAC   PM86374

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM86374   DSN@XAZP DSNDQWPZ DSNDQW05 DSNLXRSS DSNTIDXA DSNTIDXB
                 DSNTINST DSNTXAZP DSNWZIFA DSNXRIHB DSNXRIHD DSNXRIHR
                 DSNXRIHS DSN6FAC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNLXRSS
       DSNTXAZP
       DSNWZIFA
       DSNXRIHB
       DSNXRIHD
       DSNXRIHR
       DSNXRIHS

      MACROS
       DSN@XAZP
       DSNDQWPZ
       DSNDQW05
       DSNTIDXA
       DSNTIDXB
       DSNTINST
       DSN6FAC

      LISTEND
 UK94766 COVER LETTER END


 UK94778 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM82757 -
        ****************************************************************
1       * USERS AFFECTED: DB2 10 for z/OS users of REOPT(ALWAYS) and   *
        *                 APCOMPARE(ERROR/WARN)                        *
        ****************************************************************
        * PROBLEM DESCRIPTION: DB2 may fail a BIND or REBIND with the  *
        *                      bind options APCOMPARE(ERROR) and       *
        *                      REOPT(ALWAYS), or give a warning        *
        *                      message to a BIND or REBIND with the    *
        *                      bind options APCOMPARE(WARN) and        *
        *                      REOPT(ALWAYS) if there are queries with *
        *                      host variables, parameter markers or    *
        *                      special registers in the package and    *
        *                      the queries choose different access     *
        *                      paths from the prior BIND or REBIND.    *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        DB2 may fail a BIND or REBIND with the options APCOMPARE(ERROR)
        and REOPT(ALWAYS), or give a warning message to a BIND or REBIND
        with the options APCOMPARE(WARN) and REOPT(ALWAYS) if there are
        queries with host variables, parameter markers or special
        registers in the package and the queries choose different access
        paths from the prior BIND or REBIND.

        In fact, the access path of a query with host variables,
        parameter markers or special registers will be determined at
        query execution time if REOPT(ALWAYS) is specified.  Access
        path comparison could be not performed at the bind time.  The
        error or warning messages are not issued correctly.

        Additional Keywords:
        SQLACCESSPATH SQLPERFORMANCE APCOMPARE REOPT MSGDSNT285I
        Code has been modified to skip access path comparison for the
        query with host variables, parameter markers or special
        registers if APCOMPARE(ERROR) or APCOMPARE(WARN) and
        REOPT(ALWAYS) are specified for a BIND or REBIND. The query is
        counted as count-3 "STATEMENTS WHERE COMPARISON COULD NOT BE
        PERFORMED" in the message DSNT285I. There will be no access
        path comparison result in PLAN_TABLE.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM82757
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOOP   PM82757
       DSNXOPB   PM82757

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM82757   DSNXOOP  DSNXOPB

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOOP
       DSNXOPB
1
      LISTEND
 UK94778 COVER LETTER END


 UK94786 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86863 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 and 10 users of the                *
        *                 DB2 Unified Debugger.                        *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00E70005 AT DSNXESTR         *
        *                      :M101 FOR A DECLARE CURSOR              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        During DB2 unified debugger processing, a control block was left
        in an inconsistent state while doing cleanup for a table UDF
        that was called in a cursor within the stored procedure.
        DB2 code has been corrected to no longer leave the internal
        control block in the inconsistent state noted above.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM86863
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXESTR  PM86863

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM86863   DSNXESTR

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXESTR

      LISTEND
 UK94786 COVER LETTER END


 UK94806 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM73034 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of UNLOAD utility  *
        *                 with SPANNED YES or LOAD utility with        *
        *                 FORMAT SPANNED YES                           *
        ****************************************************************
        * PROBLEM DESCRIPTION: UNLOAD table space with LOB column      *
        *                      using SPANNED YES option, resulted in   *
        *                      MSGDSNU038I and ABEND04E RC00E40079.    *
        *                                                              *
        *                      IDCAMS shows zero rows in SYSREC        *
1       *                      after UNLOAD SPANNED YES.               *
        *                                                              *
        *                      LOAD with FORMAT SPANNED YES results    *
        *                      in ABEND0C4 RC00000004 after XMIT of    *
        *                      the SYSREC data set.                    *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        UNLOAD with SPANNED YES might cause DSNU038I - BLOCK SIZE FOR
        DCB, DDNAME ddname, IS TOO SMALL, MUST BE AT LEAST nnn BYTES
        and ABEND04E RC00E40079.  This abend can occur if the length of
        the base row data is longer than the block size of SYSREC.
        In some cases the block size is determined by the system.

        IDCAMS shows zero rows in SYSREC after UNLOAD SPANNED YES due to
        incorrect format of VBS data set record segments.

        LOAD FORMAT SPANNED YES results in ABENDS0C4 RC00000004
        (DSNURWBG OFFSET9A32) after XMIT of SYSREC data set.  The SYSREC
        was generated by UNLOAD SPANNED YES, but the XMIT reformatted
        the VBS segments so that LOAD did not understand the data.
        Modified UNLOAD code to be sensitive to the block size when
        writing the base row and LOB/XML data.

        Modified LOAD code to be independent of the location of data
        in the segments of the VBS data set.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM73034
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        The PTF for APAR PM73034 has modified CSECTs in both the
        DSNUT101 and DSNUTILA load modules, affecting the utility
        batch and DB2 DBM1 address spaces.  After the PTF has been
        applied, it will become active in the utility batch address
        space immediately upon job submission, while it will not take
        effect in the DB2 DBM1 address space until DB2 is stopped and
        started.

        The PTF does not have to be applied to all members in a data
        sharing environment simultaneously, and may be staged across
        each member.  However, until the fix is active in both the
        utility batch and DB2 DBM1 address spaces, the problem the PTF
        addresses will not be resolved.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNURELD  PM73034
       DSNURILD  PM73034
       DSNUROFL  PM73034
       DSNURPLD  PM73034
       DSNURPLL  PM73034
       DSNURPPD  PM73034
       DSNURWBF  PM73034
       DSNURWBG  PM73034
       DSNURWI   PM73034
1      DSNURWRF  PM73034
       DSNUULIA  PM73034
       DSNUULMB  PM73034

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM73034   DSNURELD DSNURILD DSNUROFL DSNURPLD DSNURPLL DSNURPPD
                 DSNURWBF DSNURWBG DSNURWI  DSNURWRF DSNUULIA DSNUULMB

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNURELD
       DSNURILD
       DSNUROFL
       DSNURPLD
       DSNURPLL
       DSNURPPD
       DSNURWBF
       DSNURWBG
       DSNURWI
       DSNURWRF
       DSNUULIA
       DSNUULMB

      LISTEND
 UK94806 COVER LETTER END


 UK94814 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM87677 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of DBCLOB Large    *
        *                 Objects in a distributed environment with    *
        *                 progressive streaming option.                *
        ****************************************************************
        * PROBLEM DESCRIPTION: When running DB2 applications in a      *
        *                      distributed environment with the        *
        *                      progressive streaming option, DB2 can   *
        *                      return an incorrect result for queries  *
        *                      that contain a nested loop join with an *
        *                      outer table containing a DBCLOB column. *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When running DB2 applications in a distributed environment with
        the progressive streaming option, DB2 can return an incorrect
        result for queries that involve a nested loop join if the outer
        table contains a DBCLOB column.

        The incorrect result occurs because DB2 inadvertently modifies
        an internal persistent length field for generating the character
        length.  In fact, DB2 should perform this calculation for
        character length in a separate local variable.

        The following JAVA snippet serves as an example which might
1       generate an incorrect result.

        Step 1. Define two tables, one which contains a DBCLOB column.

          CREATE DATABASE MYDBASE CCSID UNICODE;

          CREATE TABLE Primary(id integer NOT NULL,
                               short_string vargraphic(16) ,
                               long_string dbclob(16))
          IN DATABASE MYDBASE;

          CREATE TABLE Secondary(parent_id integer NOT NULL ,
                                 ordinal integer NOT NULL )
          IN DATABASE MYDBASE;


        Step 2. Insert data into the two tables.

          INSERT INTO Primary(id, short_string, long_string)
          VALUES(1, 'short string a', 'long string a');

          INSERT INTO Secondary(parent_id, ordinal) VALUES(1, 1);
          INSERT INTO Secondary(parent_id, ordinal) VALUES(1, 2);
          INSERT INTO Secondary(parent_id, ordinal) VALUES(1, 3);
          INSERT INTO Secondary(parent_id, ordinal) VALUES(1, 4);


        Step 3. Perform a query containing an inner join with the
                progressive streaming option enabled.

         try {
          String sql="SELECT id, ordinal, short_string,long_string "+
                     "FROM Primary p INNER JOIN Secondary s " +
                     "ON p.id = s.parent_id;";
          stmt = con.prepareStatement(sql);
          stmt.execute();
          ResultSet rs = stmt.executeQuery();
          while (rs.next())
           {
           System.out.println(rs.getInt(1) + "," + 
rs.getInt(2)+","+
 
           rs.getString(3) + "," + rs.getString(4));
           }
          rs.close();
          con.commit();
             } catch (SQLException e) {
          System.out.println("**SQLException in CALL simple 
proc!"+e);
 
          System.out.println("***SQLCODE = " + e.getErrorCode());
          System.out.println("***SQLSTATE = " + e.getSQLState());
          System.out.println("***Text of Error Message = "
           + e.getMessage());
          }

        The code in DB2 has been modified to prevent returning an
        incorrect result for the case described.

        Additional Keywords: SQLLOB SQLDDF SQLNLJ
1                            SQLINCORR INCORROUT SQLINCORROUT
                             DB2INCORR/K

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM87677
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNOLMAT  PM87677

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM87677   DSNOLMAT

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNOLMAT

      LISTEND
 UK94814 COVER LETTER END


 UK94828 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM84858 -
        ****************************************************************
        * USERS AFFECTED: All DB2 users of SET CURRENT PACKAGE PATH    *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00E2000C at                  *
        *                      LOC=DSNHXLTR DSNSVSVB +0AC2             *
        *                      can happen when executing               *
        *                      SET CURRENT PACKAGE PATH in a loop      *
        *                      with package-path blank or zero length  *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        DB2 acquires internal storage to process the CURRENT PACKAGE
        PATH.  When the package path is set to blanks or a zero length
        character string, this processing is not required.  DB2 was
        not freeing this storage in this case.

        Additional Keywords:
        SQLSPECIALREG
        DB2STGLK/K
        DB2 is changed to free the unused storage acquired for PACKAGE
        PATH processing when the package path is blank or a zero length
        string
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM84858
    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      DSNXESPP  PM84858

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM84858   DSNXESPP

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXESPP

      LISTEND
 UK94828 COVER LETTER END


 UK94837 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89209 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of queries which   *
        *                 use parallelism and RID sorting.             *
        ****************************************************************
        * PROBLEM DESCRIPTION: An ABEND04E rc00E70005 can occur at     *
        *                      location DSNXRRID m104 when a query is  *
        *                      being executed with parallelism and a   *
        *                      parallel group is stopped for a child   *
        *                      task performing sort processing of      *
        *                      RIDs.                                   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An ABEND04E rc00E70005 can occur at location DSNXRRID m104 when
        a query, running with parallelism, has a parallel group stopped
        for a child task performing sort processing of RIDs.

        This error check should be bypassed so that the parent task will
        continue accordingly.
        The code in DB2 has been modified to bypass issuing the abend
        error when it detects that a parallel group has been stopped.

        Additional Keywords: SQLPARALLELISM SQLSORT DB2PARALL/K
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89209
    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  PM89209

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89209   DSNXRRID

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXRRID
1
      LISTEND
 UK94837 COVER LETTER END


 UK94845 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM84153 -
        ****************************************************************
        * USERS AFFECTED: DB2 for z/OS users whose queries utilize     *
        *                 table expressions.                           *
        ****************************************************************
        * PROBLEM DESCRIPTION: Incorrect output may occur if an ORDER  *
        *                      BY expression with DESC is specified    *
        *                      inside a table expression and the       *
        *                      table expression is materialized for    *
        *                      merge scan join.                        *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        If the query specifies an ORDER BY expression with DESC inside
        a table expression and the table expression is materialized
        for merge scan join, incorrect output may occur.

        For example, incorrect output may occur for the following
        query if the table expression T3 is materialized and merge
        scan joins to table T4:

        SELECT T3.C1, T4.C1
        FROM (SELECT C1||' '
              FROM ((SELECT T1.C1||' '
                    FROM T1
                    )
                    UNION ALL
                    (SELECT T11.C1||' '
                     FROM T11
                    )
                   ) AS T2(C1)
              ORDER BY C1||' ' DESC
              GROUP BY C1||' '
             )AS T3(C1), T4
        WHERE T3.C1 = T4.C1
        GROUP BY T3.C1, T4.C1;


        Additional Keywords:
        SQLTABLEEXPR SQLORDERBY SQLACCESSPATH SQLPERFORMANCE
        SQLINCORR INCORROUT SQLINCORROUT DB2INCORR/K SQLSMJ SQLMSJ
        SMJ MSJ

        Code is changed to correct the incorrect output problem
        for the situation described above.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM84153
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
1                LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM84153:

        See PM84153 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM84153 corrects a problem that incorrect output may occur if
        an ORDER BY expression with DESC is specified in a table
        expression and the table expression is materialized for
        merge scan join.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOPCO  PM84153

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM84153   DSNXOPCO

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOPCO

      LISTEND
 UK94845 COVER LETTER END


 UK94861 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88703 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of the RANK and    *
        *                 DENSE_RANK window functions in the OLAP      *
        *                 specification.                               *
        ****************************************************************
        * PROBLEM DESCRIPTION: An incorrect result can be returned for *
        *                      an SQL statement that contains the      *
        *                      RANK and DENSE_RANK window functions.   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The RANK and DENSE_RANK window functions can return an incorrect
        result set when the argument contains a padded string.

        The following simple example illustrates a failing case.

        Step 1. Create Table T1 and insert three rows.

          CREATE TABLE T1(C_CHA CHAR(2), C_VARC VARCHAR(2));

          INSERT INTO T1 VALUES('A','AA');
1         INSERT INTO T1 VALUES('A','AA');
          INSERT INTO T1 VALUES('AA','A');


        Step 2. Select from Table T1 using the RANK and DENSE_RANK
        OLAP functions.

          SELECT C_CHA AS OBY,
                 C_VARC||C_CHA AS PBY,
                 RANK() OVER(
                             PARTITION BY C_VARC||C_CHA
                             ORDER BY C_CHA
                             ) AS RANK1,
                 DENSE_RANK() OVER(
                             PARTITION BY C_VARC||C_CHA
                             ORDER BY C_CHA
                             ) AS DENSE_RANK1
          FROM T1;


        Step 3. Check the results.

        The following incorrect result is returned.  The 3rd row is not
        as expected.  The RANK1 and DENSE_RANK1 values for the 3rd row
        should be 3 and 2.

          +--------------------------------------------------
          | OBY | PBY  | RANK1          | DENSE_RANK1       |
          +--------------------------------------------------
        1_| A   | AAA  |              1 |                 1 |
        2_| A   | AAA  |              1 |                 1 |
        3_| AA  | AAA  |              1 |                 1 |
          +--------------------------------------------------

        This problem occurs because DB2 doesn't handle the padding
        character properly for the input argument to the RANK and
        DENSE_RANK window functions.
        DB2 code is modified to use correct padding character for the
        argument for RANK and DENSE_RANK window functions.

        Additional Keywords: SQLINCORR SQLINCORROUT INCORROUT
                             DB2INCORR/K SQLRANK SQLDENSERANK
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88703
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXRWND  PM88703

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88703   DSNXRWND

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

1     MODULES
       DSNXRWND

      LISTEND
 UK94861 COVER LETTER END


 UK94868 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM84206 -
        ****************************************************************
        * USERS AFFECTED: DB2 data sharing users.                      *
        ****************************************************************
        * PROBLEM DESCRIPTION: After canceling a job which updates a   *
        *                      GBP-dependent LOB space, a page of the  *
        *                      LOB may be put into LPL by DSNB5SCM.    *
        *                      The page later gets put into the write  *
        *                      error page range (WEPR), so LPL         *
        *                      recovery cannot repair it.              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        If an application is canceled while updating a GBP-dependent LOB
        page, and the LOB page is marked "broken", the begin-abort
        processing will schedule online page recovery asynchronously.
        This process will have to wait for the application to commit
        since it requires a drain.  Meanwhile, the application's commit
        processing cannot write the broken page and puts it into LPL.
        Then the online recovery gets control, but cannot recover the
        page since it is now in LPL.  So the failed recovery puts it
        into the write error page range, which requires the RECOVER
        utility to fix it.
        The begin-abort processing for a broken LOB page has been
        modified to perform the online recovery synchronously, as is
        done for non-LOB objects.  This will prevent having the broken
        page put into LPL and WEPR.  The online recovery logic has been
        modified to handle LOB objects correctly for the synchronous
        case (needs to preserve the invoker's write intent).
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM84206
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNB1CFC  PM84206
       DSNB1RTR  PM84206

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM84206   DSNB1CFC DSNB1RTR

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNB1CFC
       DSNB1RTR
1
      LISTEND
 UK94868 COVER LETTER END


 UK94915 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM87227 -
        ****************************************************************
        * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
        ****************************************************************
        * PROBLEM DESCRIPTION: SQLCODE -904 is correctly returned      *
        *                      when a Communications DataBase (CDB)    *
        *                      unavailable condition occurs, however   *
        *                      the reason code returned does not       *
        *                      reflect the actual error condition.     *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When attempting to access a remote server using a trusted
        connection, DB2 searches the CDB for the system authid to be
        used in connecting to the remote location.  If an error occurs,
        such as an ASUTIME limit exceeded condition, DB2 reports the
        error with SQLCODE -904 but with an incorrect reason code,
        00D3102E (trusted context system authid row not found),
        instead of a reason code that reflects the actual error.

        DB2 has been changed to report the reason code associated
        with the actual error.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM87227
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNLVINF  PM87227

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM87227   DSNLVINF

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNLVINF

      LISTEND
 UK94915 COVER LETTER END


 UK94916 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM85880 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 and 10 for z/OS users of DROP      *
        *                 ALIAS.                                       *
1       ****************************************************************
        * PROBLEM DESCRIPTION: DROP ALIAS may fail to invalidate       *
        *                      dependent plans and packages when       *
        *                      running concurrently with DML that      *
        *                      references the same alias.              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        DROP ALIAS running concurrently with DML that references the
        same alias may result in orphaned rows in SYSIBM.SYSPACKDEP
        and SYSIBM.SYSPLANDEP if DB2 fails to invalidate dependent
        plans and packages as a result of a timing window problem.

        DROP ALIAS running concurrently with CREATE MASK or CREATE
        PERMISSION which references the same alias may result in
        orphaned rows in SYSIBM.SYSDEPENDENCIES as a result of a
        timing window problem. Furthermore, operations against any
        row permissions or masks referencing the base table, such as
        ALTER REGENERATE or SELECT, may fail if any objects that are
        referenced in the row permission definition or column mask
        definition no longer exist.
        PM85880 fixes a timing window which may result in the
        following orphaned rows:
         o SYSIBM.SYSPACKDEP and SYSIBM.SYSPLANDEP records if DB2
           fails to invalidate dependent plans and packages when
           DROP ALIAS is run concurrently with DML referencing the
           same alias.
         o SYSIBM.SYSDEPENDENCIES records when DROP ALIAS is run
           concurrently with CREATE MASK or CREATE PERMISSION
           referencing the same alias.

        With PM85880 applied, concurrently running statements
        referencing the alias being dropped may result in SQLCODE -911
        or SQLCODE -904.

        ADDITIONAL KEYWORDS:
        SQLCODE911
        SQLCODE904
        SQLDROP
        SQLINSERT
        SQLUPDATE
        SQLSELECT

        ++HOLD COMMENT FOR RELEASE A10, TYPE ACT:
        PM85880 fixes a timing window which may result in the
        following orphaned rows:
         o SYSIBM.SYSPACKDEP and SYSIBM.SYSPLANDEP records if DB2
           fails to invalidate dependent plans and packages when
           DROP ALIAS is run concurrently with DML referencing the
           same alias.
         o SYSIBM.SYSDEPENDENCIES records when DROP ALIAS is run
           concurrently with CREATE MASK or CREATE PERMISSION
           referencing the same alias.

        With PM85880 applied, concurrently running statements
        referencing the alias being dropped may result in SQLCODE -911
1       or SQLCODE -904.

        This apar does not fix existing orphaned SYSIBM.SYPACKDEP,
        SYSIBM.SYSPLANDEP or SYSIBM.SYSDEPENDENCIES records. If
        orphaned SYSIBM.SYPACKDEP or SYSIBM.SYSPLANDEP rows are
        identified, remove any reference of the dropped alias and
        rebind plans and packages. If SYSIBM.SYSDEPENDENCIES
        rows are identified, the dependent mask or permission will
        need to be dropped and recreated without referencing the
        dropped alias.

        The following queries are provided as examples of how to
        identify the orphaned records.

         QUERY1
         ------
         SYSPLANDEP records the dependencies that a given plan has on
         other DB2 objects. For every row in SYSPLANDEP that indicates
         a dependency upon an alias, there should be a corresponding
         row in SYSTABLES.

         SELECT BNAME, BCREATOR, BTYPE, DNAME
           FROM SYSIBM.SYSPLANDEP PD
           WHERE BTYPE IN ('A')
             AND NOT EXISTS
               (SELECT *
                  FROM SYSIBM.SYSTABLES
                  WHERE CREATOR = PD.BCREATOR
                    AND NAME = PD.BNAME
                    AND TYPE = PD.BTYPE);

         QUERY2
         ------
         SYSPACKDEP records the dependencies that a given package has
         on other DB2 objects. For every row in SYSPACKDEP that
         indicates a dependency upon an alias, there should be a
         corresponding row in SYSTABLES.

         SELECT BNAME, BQUALIFIER, BTYPE, DNAME
           FROM SYSIBM.SYSPACKDEP PD
           WHERE BTYPE IN ('A')
             AND NOT EXISTS
               (SELECT *
                  FROM SYSIBM.SYSTABLES
                  WHERE CREATOR = PD.BQUALIFIER
                    AND NAME = PD.BNAME
                    AND TYPE = PD.BTYPE );

         QUERY3
         ------
         SYSDEPENDENCIES records the dependencies between objects. For
         every row in SYSDEPENDENCIES that indicates a dependency upon
         an alias, there should be a corresponding row in SYSTABLES.

         SELECT *
           FROM SYSIBM.SYSDEPENDENCIES DEP
1          WHERE BTYPE IN ('A')
             AND NOT EXISTS
               (SELECT *
                  FROM SYSIBM.SYSTABLES
                  WHERE CREATOR = DEP.BSCHEMA
                    AND NAME = DEP.BNAME
                    AND TYPE = DEP.BTYPE);



        ++HOLD COMMENT FOR RELEASE 910, TYPE ACT:
        PM85880 fixes a timing window which may result in orphaned
        SYSIBM.SYSPACKDEP and SYSIBM.SYSPLANDEP records if DB2
        fails to invalidate dependent plans and packages when
        DROP ALIAS is run concurrently with DML referencing the
        same alias.

        With PM85880 applied, concurrently running statements
        referencing the alias being dropped may result in SQLCODE -911
        or SQLCODE -904.

        This apar does not fix existing orphaned SYSIBM.SYPACKDEP or
        SYSIBM.SYSPLANDEP records. If orphaned SYSIBM.SYPACKDEP or
        SYSIBM.SYSPLANDEP rows are identified, remove any reference
        of the dropped alias and rebind plans and packages.

        The following queries are provided as examples of how to
        identify the orphaned records.

         QUERY1
         ------
         SYSPLANDEP records the dependencies that a given plan has on
         other DB2 objects. For every row in SYSPLANDEP that indicates
         a dependency upon an alias, there should be a corresponding
         row in SYSTABLES.

         SELECT BNAME, BCREATOR, BTYPE, DNAME
           FROM SYSIBM.SYSPLANDEP PD
           WHERE BTYPE IN ('A')
             AND NOT EXISTS
               (SELECT *
                  FROM SYSIBM.SYSTABLES
                  WHERE CREATOR = PD.BCREATOR
                    AND NAME = PD.BNAME
                    AND TYPE = PD.BTYPE);

         QUERY2
         ------
         SYSPACKDEP records the dependencies that a given package has
         on other DB2 objects. For every row in SYSPACKDEP that
         indicates a dependency upon an alias, there should be a
         corresponding row in SYSTABLES.

         SELECT BNAME, BQUALIFIER, BTYPE, DNAME
           FROM SYSIBM.SYSPACKDEP PD
           WHERE BTYPE IN ('A')
1            AND NOT EXISTS
               (SELECT *
                  FROM SYSIBM.SYSTABLES
                  WHERE CREATOR = PD.BQUALIFIER
                    AND NAME = PD.BNAME
                    AND TYPE = PD.BTYPE );
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM85880
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        PM85880 fixes a timing window which may result in the
        following orphaned rows:
         o SYSIBM.SYSPACKDEP and SYSIBM.SYSPLANDEP records if DB2
           fails to invalidate dependent plans and packages when
           DROP ALIAS is run concurrently with DML referencing the
           same alias.
         o SYSIBM.SYSDEPENDENCIES records when DROP ALIAS is run
           concurrently with CREATE MASK or CREATE PERMISSION
           referencing the same alias.

        With PM85880 applied, concurrently running statements
        referencing the alias being dropped may result in SQLCODE -911
        or SQLCODE -904.

        This apar does not fix existing orphaned SYSIBM.SYPACKDEP,
        SYSIBM.SYSPLANDEP or SYSIBM.SYSDEPENDENCIES records. If
        orphaned SYSIBM.SYPACKDEP or SYSIBM.SYSPLANDEP rows are
        identified, remove any reference of the dropped alias and
        rebind plans and packages. If SYSIBM.SYSDEPENDENCIES
        rows are identified, the dependent mask or permission will
        need to be dropped and recreated without referencing the
        dropped alias.

        The following queries are provided as examples of how to
        identify the orphaned records.

         QUERY1
         ------
         SYSPLANDEP records the dependencies that a given plan has on
         other DB2 objects. For every row in SYSPLANDEP that indicates
         a dependency upon an alias, there should be a corresponding
         row in SYSTABLES.

         SELECT BNAME, BCREATOR, BTYPE, DNAME
           FROM SYSIBM.SYSPLANDEP PD
           WHERE BTYPE IN ('A')
             AND NOT EXISTS
               (SELECT *
                  FROM SYSIBM.SYSTABLES
                  WHERE CREATOR = PD.BCREATOR
                    AND NAME = PD.BNAME
                    AND TYPE = PD.BTYPE);

         QUERY2
1        ------
         SYSPACKDEP records the dependencies that a given package has
         on other DB2 objects. For every row in SYSPACKDEP that
         indicates a dependency upon an alias, there should be a
         corresponding row in SYSTABLES.

         SELECT BNAME, BQUALIFIER, BTYPE, DNAME
           FROM SYSIBM.SYSPACKDEP PD
           WHERE BTYPE IN ('A')
             AND NOT EXISTS
               (SELECT *
                  FROM SYSIBM.SYSTABLES
                  WHERE CREATOR = PD.BQUALIFIER
                    AND NAME = PD.BNAME
                    AND TYPE = PD.BTYPE );

         QUERY3
         ------
         SYSDEPENDENCIES records the dependencies between objects. For
         every row in SYSDEPENDENCIES that indicates a dependency upon
         an alias, there should be a corresponding row in SYSTABLES.

         SELECT *
           FROM SYSIBM.SYSDEPENDENCIES DEP
           WHERE BTYPE IN ('A')
             AND NOT EXISTS
               (SELECT *
                  FROM SYSIBM.SYSTABLES
                  WHERE CREATOR = DEP.BSCHEMA
                    AND NAME = DEP.BNAME
                    AND TYPE = DEP.BTYPE);
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXIDAL  PM85880

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM85880   DSNXIDAL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXIDAL

      LISTEND
 UK94916 COVER LETTER END


 UK94918 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM87363 -
        ****************************************************************
        * USERS AFFECTED: DB2 10 for z/OS users of ALTER TABLESPACE.   *
        ****************************************************************
        * PROBLEM DESCRIPTION: User receives ABEND04E RC00C20305       *
        *                      in DSNB1LCM +09AA on an ALTER           *
        *                      TABLESPACE MAXPARTITIONS statement.     *
1       ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        ABEND04E RC00C20305 DSNIDM DSNB1LCM +09AA received during
        ALTER TABLESPACE MAXPARTITIONS processing when concurrent DML
        is executing against the table space.  The abend occurs due to
        DB2 incorrectly serializing the ALTER TABLESPACE execution
        with the concurrent DML.  While this APAR addresses a specific
        reported symptom, other symptoms are possible.
        DB2 has been changed to obtain an X-lock on the SYSTABLESPACE
        row during execution of ALTER TABLESPACE, serializing execution
        of ALTER TABLESPACE with concurrent DML on the table space.
        With PM87363 applied, concurrently running DML referencing a
        table space being altered may result in SQLCODE -911 or
        SQLCODE -904.

        ADDITIONAL KEYWORDS:
        SQLCODE911
        SQLCODE904
        SQLALTER
        OFFSET09AA
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM87363
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXIATS  PM87363
       DSNXISB1  PM87363

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM87363   DSNXIATS DSNXISB1

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXIATS
       DSNXISB1

      LISTEND
 UK94918 COVER LETTER END


 UK94919 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89383 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 10 for z/OS who are also    *
        *                 using IBM DB2 Analytics Accelerator.         *
        ****************************************************************
        * PROBLEM DESCRIPTION: An INSERT with subselect statement      *
        *                      may be incorrectly blocked from         *
        *                      offload to an accelerator.              *
        ****************************************************************
        * RECOMMENDATION:                                              *
1       ****************************************************************
        An INSERT with subselect statement may be incorrectly blocked
        from offload to an accelerator.  EXPLAIN of the SQL statement
        will have DSN_QUERYINFO_TABLE.REASON_CODE=3 and
        DSN_QUERYINFO_TABLE.QI_DATA='The query is a DB2 short running
        query or offloading is not advantageous.'

        For example:

        INSERT INTO T1
        SELECT C1,C2,COUNT(*)
        FROM T2 GROUP BY C1, C2;



        Code is fixed to properly determine if an INSERT with select
        statement should offload or not.

        Additional Search Keywords:
        IDAAV3R1/K SQLINSWSELECT
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89383
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXONZH  PM89383

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89383   DSNXONZH

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXONZH

      LISTEND
 UK94919 COVER LETTER END


 UK94920 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89194 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users *
        *                 of queries with XML functions and GROUP BY   *
        *                 when running in CM8 mode.                    *
        ****************************************************************
        * PROBLEM DESCRIPTION: An ABEND04E RC00E72098 at DSNXSORI      *
        *                      +47BE for a query with XML functions    *
        *                      and a GROUP BY when in either V9 CM8    *
        *                      mode or V10 CM8 mode.                   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
1       An ABEND04E RC00E72098 at DSNXSORI +47BE for a query with XML
        functions and GROUP BY when in either v9 CM8 mode or v10 CM8
        mode. This query may have worked in v8; but in a later release
        of DB2, this abend may occur if some XML functions are included.
        The size of the internal representation of the XML functions
        changed from 16 bytes to 64 bytes in v9.

        In v8, this query may have been successful in sort since
        the length of the row may have been under 4032 bytes (tag sort
        limit).  But in v9 NFM or later, the size changed to 64 bytes.
        If there is a GROUP BY, the query may now try to use a tag
        sort, Since the row increased in size, it could now cause
        the abend.
        DB2 has been modified to remove the check for the level of DB2
        when checking if there is a GROUP BY and a possible tag sort.

        Additional keywords: TAGSORT SQLGROUPBY SQLXML OFFSET47BE
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89194
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXSORI  PM89194

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89194   DSNXSORI

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXSORI

      LISTEND
 UK94920 COVER LETTER END


 UK94931 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM85850 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users *
        *                 of LOAD FORMAT DELIMITED with partition      *
        *                 parallelism                                  *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C4 RC00000038 DSNURPLD OFFSET23C4 *
        *                      or ABEND0C4 RC00000010 DSNUGSTB         *
        *                      OFFSET1508 during a partition parallel  *
        *                      LOAD utility with FORMAT DELIMITED      *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        User ran a LOAD FORMAT DELIMITED INTO TABLE PART X INDDN utility
        with partition parallelism. When one of the load subtask was
        assigned two partitions and the LRECL of the input dataset for
1       the first partition is smaller than the second one, an overlay
        happened which caused ABENDS0C4 RC00000038 at
        DSNURPLD + x'23C4'.

        The reported problem was caused by the LOAD utility not
        allocating a sufficiently large enough work area for record
        processing.

        Additional symptom: DSNUGSTB + x'1508'
        The LOAD partition parallelism code has been modified to
        allocate a sufficiently large work area for FORMAT DELIMITED
        processing
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM85850
    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  PM85850
       DSNURPLD  PM85850

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM85850   DSNURILD DSNURPLD

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNURILD
       DSNURPLD

      LISTEND
 UK94931 COVER LETTER END


 UK94952 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM87836 -
        ****************************************************************
        * USERS AFFECTED: DB2 10 for z/OS users who use                *
        *                 DSN_PREDICAT_TABLE and/or                    *
        *                 DSN_DETCOST_TABLE                            *
        ****************************************************************
        * PROBLEM DESCRIPTION: DSN_DETCOST_TABLE may have incorrect    *
        *                      cost fields.                            *
        *                      DSN_PREDICAT_TABLE may have incorrect   *
        *                      UNCERTAINTY values for table compare    *
        *                      predicates.                             *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        1. DSN_DETCOST_TABLE may have incorrect estimated cost values
           in various columns.  Arithmetic computations of the filter
           factor sometimes use the wrong precision, which can lead to
           the incorrect estimated cost values.
        2. DSN_PREDICAT_TABLE may have incorrect UNCERTAINTY values for
1          table compare predicates due to an uninitialized variable.

           For example,

           SELECT C2 FROM T1
             GROUP BY C2
             HAVING
             SUM(C2 * C1) > (SELECT SUM(C3 * C4) * 0.001 FROM T1)

        Additional Keywords:
        SQLEXPLAIN
        Problems with incorrect values in DSN_PREDICAT_TABLE and
        DSN_DETCOST_TABLE are fixed.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM87836
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM87836:

        See PM87836 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM87836 corrects problems of incorrect UNCERTAINTY values in
        DSN_PREDICAT_TABLE and incorrect cost fields in
        DSN_DETCOST_TABLE.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM69139:

        See PM69139 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM69139 corrects a problem of inaccurate compound filter
        factor of two range predicates on the same column that may
        result in an inefficient access path.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM64315:

        A rebind is necessary for static applications to rebuild
        access paths based on the changes in this APAR.

        PM64315 corrects a problem in which the filter factor for a
        compound predicate containing an OR predicate could be
        overestimated.  The incorrect compound filter factor could
        result in an inefficient access path and resulting poor query
1       performance.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM61658:

        See PM61658 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM61658 corrects a problem of over-estimated correlated
        subquery cardinality when global query optimization
        is enabled (OPTXQB=ON) and there are materialized views
        involved in the join between the parent query block and the
        correlated subquery.  This may result in an inefficient access
        path.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM56435:

        A rebind is necessary for static applications to rebuild
        access paths based on changes in this APAR.

        PM56435 corrects a problem in which DB2 could compute an
        incorrect compound filter factor.  This could lead to an
        inefficient access path and poor query performance.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM44942:

        See PM44942 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM44942 corrects a problem of a poorly performing access path
        caused by incorrect filter factor estimation for a compound
        predicate when frequency or histogram statistics exist, or
        column cardinality is 1 or 2.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM32384:

        See PM32384 APAR/PTF text for additional information about
1       why a REBIND is necessary.

        PM32384 corrects a problem of inaccurate index filter factor
        estimate when multi-column cardinality exists in some cases
        which may result in an inefficient access path.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      ACTION:
        PM87836 does not correct the incorrect values that are already
        in DSN_DETCOST_TABLE and DSN_PREDICAT_TABLE.  The incorrect
        values may or may not be readily identifiable as incorrect
        by simple visual inspection.
        To get the correct values, apply this fix.  Then, delete the
        old rows in DSN_DETCOST_TABLE and DSN_PREDICAT_TABLE.
        EXPLAIN the statements again to re-populate the
        DSN_DETCOST_TABLE and DSN_PREDICAT_TABLE with the correct
        values.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOCCF  PM87836
       DSNXODFT  PM87836

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM87836   DSNXOCCF DSNXODFT

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOCCF
       DSNXODFT

      LISTEND
 UK94952 COVER LETTER END


 UK94967 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM83978 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of                 *
        *                 ALTER TABLE ADD PARTITION.                   *
        ****************************************************************
        * PROBLEM DESCRIPTION: Slow performance during ALTER TABLE     *
        *                      ADD PARTITION processing.               *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available.         *
        ****************************************************************
        Slow performance during ALTER TABLE ADD PARTITION. During the
        ALTER TABLE ADD PARTITION process, a service is invoked to
        delete SYSIBM.SYSLGRNX records for the partition being added.
        Residual records could exist due to a previous ALTER TABLE ADD
        PARTITION that failed. This service uses directory index
        SYSIBM.DSNLLX02, which does not contain partition number as
1       part of the index key, which contributed to the slow
        performance.
        The service that deletes SYSLGRNX records during ALTER TABLE
        ADD PARTITION processing has been modified to use index
        SYSIBM.DSNLLX01 for better performance.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM83978
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUADP2  PM83978

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM83978   DSNUADP2

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUADP2

      LISTEND
 UK94967 COVER LETTER END


 UK94999 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM85375 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 9 for z/OS or DB2 10 for    *
        *                 z/OS who use DSNTEP2 or DSNTEP4 to process   *
        *                 SQL statements that are preceded by 'EXEC    *
        *                 SQL'.                                        *
        ****************************************************************
        * PROBLEM DESCRIPTION: This APAR addresses three problems that *
        *                      can occur when DSNTEP2 and DSNTEP4 are  *
        *                      used to process SQL statements that are *
        *                      preceded by 'EXEC SQL':                 *
        *                                                              *
        *                      (1) Response messages for SQL           *
        *                          statements say 'EXEC' instead of    *
        *                          identifying the actual SQL verb.    *
        *                          For example,                        *
        *                            EXEC SQL SET CURRENT SQLID        *
        *                              = 'auth-ID';                    *
        *                          results in                          *
        *                            EXEC      SUCCESSFUL              *
        *                          instead of                          *
        *                            SET       SUCCESSFUL              *
        *                                                              *
        *                      (2) Response messages for DELETE,       *
        *                          INSERT, and UPDATE statements say   *
        *                          'EXEC SUCCESSFUL' instead of        *
        *                          giving the number of rows affected  *
        *                          and identifying the SQL verb.  For  *
1       *                          example:                            *
        *                            EXEC SQL UPDATE MY.TABLE          *
        *                              SET C1 = 'x';                   *
        *                          results in                          *
        *                            EXEC      SUCCESSFUL              *
        *                          instead of                          *
        *                            SUCCESSFUL UPDATE    OF           *
        *                              n ROW(S)                        *
        *                                                              *
        *                      (3) Static SQL statements supported     *
        *                          by DSNTEP2 and DSNTEP4 (CONNECT,    *
        *                          CONNECT TO, CONNECT RESET, SET      *
        *                          CONNECTION, RELEASE location,       *
        *                          RELEASE ALL, RELEASE ALL SQL,       *
        *                          RELEASE CURRENT, and RELEASE ALL    *
        *                          PRIVATE) fail with SQLCODE -84      *
        *                          (UNACCEPTABLE SQL STATEMENT).       *
        *                                                              *
        *                          Note: RELEASE ALL PRIVATE is not    *
        *                          supported in DB2 10.                *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available.         *
        ****************************************************************
        DSNTEP2 and DSNTEP4 are DB2 supplied PL/I sample application
        programs that can be used to perform dynamic SQL statement
        processing in the batch mode.  These programs also support
        the static SQL statements CONNECT, SET CONNECTION, and RELEASE.
        For convenience, SQL statements can be preceded by EXEC SQL.

        Results of most SQL processing is noted in the output by status
        messages that indicate the SQL statement's verb (SET, DROP,
        etc.).  Currently, the status messages for most statements that
        are preceded by EXEC SQL use EXEC as the verb instead of the
        actual SQL verb.

        In addition, many static SQL statements supported by DSNTEP2
        and DSNTEP4 currently fail with SQLCODE -84 (UNACCEPTABLE SQL
        STATEMENT) when preceded by EXEC SQL.

        In response, this APAR modifies DSNTEP2 and DSNTEP4 to correctly
        handle incoming SQL statements that are preceded by EXEC SQL.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM85375
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        ***Action for PM85375 (V10)

        This PTF updates the source code for DSNTEP2 and DSNTEP4
        plus the shipped object decks (DSNTEP2L and DSNTEP4L) and
        shipped DBRMs (DSN@EP2L and DSN@EP4L).  These changes
        do not become effective until you rebuild the load modules
        and rebind the plans.

        * On DB2 10 systems running in conversion mode (CM) or
1         enabling-new-function mode (ENFM), no further 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.
        * On DB2 10 systems in new-function mode, proceed as
          follows:
          (a) If you use DSNTEP2 or DSNTEP4 (or both) as supplied
              by DB2, run IVP job DSNTEJ1L to relink the load
              modules from the shipped object modules and bind the
              plans from the shipped DBRMs.
          (b) If you use a modified version of DSNTEP2 or DSNTEP4
              (or both) redo your modifications and then run IVP
              job DSNTEJ1P to recompile and link-edit the load
              modules and bind the plans for DSNTEP2 and DSNTEP4.
      ACTION:
        ***Action for PM59506 (V10)

        (1) A DSNTEP2 or DSNTEP4 job that uses the parameter SQLTERM
        to specify an invalid terminator character will need to be
        modified to specify a valid terminator character.
        Any character is valid except a blank, comma, single or
        double quote, underscore, or parenthesis.

        (2) This PTF updates the source code for DSNTEP2 and DSNTEP4
        plus the shipped object decks (DSNTEP2L and DSNTEP4L) and
        shipped DBRMs (DSN@EP2L and DSN@EP4L).  These changes
        do not become effective until you rebuild the load modules
        and rebind the plans.

        * On DB2 V10 systems running in conversion mode (CM) or
          enabling-new-function mode (ENFM), no further action is
          required after applying this PTF.  The updates will be
          used when you run the V10 IVP jobs after DB2 V10 enters
          new-function mode.
        * On DB2 V10 systems in new-function mode, proceed as
          follows:
          (a) If you use DSNTEP2 or DSNTEP4 (or both) as supplied
              by DB2, run IVP job DSNTEJ1L to relink the load
              modules from the shipped object modules and bind the
              plans from the shipped DBRMs.
          (b) If you use a modified version of DSNTEP2 or DSNTEP4
              (or both) redo your modifications and then run IVP
              job DSNTEJ1P to recompile and link-edit the load
              modules and bind the plans for DSNTEP2 and DSNTEP4.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSN@EP2L  PM85375
       DSN@EP4L  PM85375
       DSNTEP2   PM85375
       DSNTEP2L  PM85375
       DSNTEP4   PM85375
       DSNTEP4L  PM85375

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM85375   DSN@EP2L DSN@EP4L DSNTEP2  DSNTEP2L DSNTEP4  DSNTEP4L

1     THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MACROS
       DSN@EP2L
       DSN@EP4L
       DSNTEP2
       DSNTEP2L
       DSNTEP4
       DSNTEP4L

      LISTEND
 UK94999 COVER LETTER END


 UK95001 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89512 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of RUNSTATS        *
        *                 with USE PROFILE keyword.                    *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C4 at DSNUSITS + x'1DA8' for      *
        *                      RUNSTATS TABLESPACE DSNDB06.SYSTSPKG    *
        *                      TABLE(SYSIBM.SYSPACKAGE) USE PROFILE    *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        When a user executed RUNSTATS TABLESPACE with USE PROFILE,
        an ABENDS0C4 at DSNUSITS OFFSET1DA8 occurred during the
        initialization for profile processing of a table space.
        The code path in error should only be executed when
        USE PROFILE is specified with the PART keyword.
        Avoid special setup meant when processing a subset of
        partitions in a partitioned table space for all cases
        that do not apply.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89512
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUSITS  PM89512

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89512   DSNUSITS

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUSITS

      LISTEND
 UK95001 COVER LETTER END


1UK95005 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88761 -
        ****************************************************************
        * USERS AFFECTED: All users of the DCLGEN facility in DB2 9    *
        *                 for z/OS and DB2 10 for z/OS are affected    *
        *                 by this APAR.                                *
        ****************************************************************
        * PROBLEM DESCRIPTION: When governed by the DB2 Resource Limit *
        *                      Facility (RLF), DCLGEN can terminate    *
        *                      with SQLCODE -495                       *
        *                        ESTIMATED PROCESSOR COST OF n         *
        *                        PROCESSOR SECONDS (x SERVICE UNITS)   *
        *                        IN COST CATEGORY y EXCEEDS A RESOURCE *
        *                        LIMIT ERROR THRESHOLD OF z SERVICE    *
        *                        UNITS                                 *
        ****************************************************************
        * RECOMMENDATION: Apply the fixing PTF for this APAR           *
        ****************************************************************
        DCLGEN generates the SQL and host-language declarations for a
        given DB2 table or view.  Currently, when DCLGEN is governed by
        the DB2 Resource Limit Facility (RLF), requests for tables or
        views that have a very large number of rows can exceed the error
        threshold value specified in the resource limit specification
        table (RLST) and fail with SQLCODE -495.
        In response, this APAR improves the efficiency of the technique
        used by DCLGEN to obtain information about the specified table
        or view.  This change prevents the SQLCODE -495.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88761
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        ***Action for PM88761 (DB2 10)

        This PTF modifies the DCLGEN tool to prevent failures caused by
        SQLCODE -495 (resource limit restrictions).

        If you have already installed or migrated to DB2 10 for z/OS
        then after applying this PTF, you need to rebind the DCLGEN
        package.  You can use the following command:

          BIND PACKAGE(DSNEDCL) MEMBER(DSNECP68) -
               ACTION(ADD) ISOLATION(CS) ENCODING(EBCDIC) -
               LIBRARY('prefix.SDSNDBRM')

        where prefix is the prefix of your DB2 10 target libraries.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSN@CP68  PM88761
       DSNECP68  PM88761

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88761   DSN@CP68 DSNECP68

1     THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNECP68

      MACROS
       DSN@CP68

      LISTEND
 UK95005 COVER LETTER END


 UK95006 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM87388 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS users of SCA rebuild        *
        *                 and partitioned table spaces that have over  *
        *                 64 partitions created, including data        *
        *                 partitioned secondary indexes (DPSI) and     *
        *                 nonpartitioned secondary indexes (NPSI) on   *
        *                 such table spaces                            *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNIDBMF ERQUAL5321 *
        *                      ABEND04E RC00C90101 DSNIDBMF ERQUAL5320 *
        *                      ABEND04E RC00C90101 DSNIDBDF ERQUAL5321 *
        *                      or similar abends may occur soon after  *
        *                      DB2 restart (bringing member down),     *
        *                      when the system has recently gone       *
        *                      through SCA rebuild                     *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The aforementioned DBET-related abends may occur in data sharing
        at some point after restart, under the following conditions:

        - A partitioned object exists with over 64 created partitions
          (could be a DPSI or NPSI index as well).

        - The object was processed during backward log recovery in a
          prior restart (e.g. a crashed utility on the object was being
          backed out during that phase) and at least one data sharing
          member was already up while this backout was being performed.

        - Later on, SCA rebuild took place, for example: SETXCF START,
          REBUILD,STRNM=DSNCAT_SCA.

        - Now a restart takes place, followed by one of the mentioned
          abends after the restart, bringing the member back down. The
          abend after restart need not be immediately after restart.
          Instead, the abend could occur whenever the object happens to
          be the target of an exception state change (e.g. issuing the
          -STOP DATABASE SPACENAM command against it, or running another
          utility against it).

        More specifically, during the backward recovery phase, the
1       member was creating a non-collapsed internal DBET structure for
        the object, while members that were up were receiving notifies
        and building a collapsed DBET structure. This is normal, however
        if a SCA rebuild was issued later on, if the member with the
        non-collapsed DBET structure was processed last by the SCA
        rebuild, an orphan DBET SCA record was produced, which during
        a subsequent restart helped build a structurally incorrect DBET
        entry (resulting in abend at some point after restart, which
        brought the member down).

        Until this fix is applied, the only known bypass to this problem
        would be to perform group restart, which will rebuild the group
        DBET in SCA from the logs.
        DB2 restart processing has been modified to detect orphaned
        group DBET records in SCA and erase these orphans. This cleaned
        up SCA-record set will then be used by DB2 to correctly build
        the local DBET structure for the object.

        Additional keywords: DB2DSHR SYSPLEXDS
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM87388
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNIDBGC  PM87388
       DSNIDBGN  PM87388
       DSNIDBNI  PM87388

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM87388   DSNIDBGC DSNIDBGN DSNIDBNI

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIDBGC
       DSNIDBGN
       DSNIDBNI

      LISTEND
 UK95006 COVER LETTER END


 UK95009 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88519 -
        ****************************************************************
        * USERS AFFECTED: All HIR2220 (IRLM220) and HIR2230 (IRLM230)  *
        *                 users data sharing SYSPLEXDS.                *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C90101 in DSNKINSL:5004    *
        *                      for duplicate key found during DB2 log  *
        *                      apply. MSGDSNB250E for LPL may appear   *
        *                      for LOGAPPLY.                           *
        ****************************************************************
1       * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
        ****************************************************************
        ABEND04E RC00C90101 may be issued during DB2 log apply process.
        This may happen in certain timing window where an Inserter is
        able to update using the same key that was deleted by the
        Deleter while the Deleter has not committed yet. If the Deleter
        rolls back, it may get the duplicate key error and abend.
        Insert/update from another member should not happen until the
        Deleter commits the delete.  There is a timing error where
        Inserter asking for an S lock request with pseudo delete check,
        will not know that a Deleter exists in the group, because the
        pseudo-delete feedback (RLPRCB10) is not always correctly set
        by IRLM when the lock request completes and returns to the
        caller.
        GEN:
        KEYWORDS:
         SYSPLEXDS

        *** END IMS KEYWORDS ***
        This APAR closes a timing window where pseudo-deleter feedback
        was not set by IRLM/XES Contention Exit code when there was
        a request from another member for the same lock, already waiting
        in the contention exit. IRLM will set RLPRCB10 correctly upon
        return to the lock requester/Inserter member to inform about
        a Deleter in the group. The Inserter will wait for the Deleter
        side to commit first, instead of going ahead itself with
        updates.
        Note PM80714 fixes a another timing exposure where there was an
        earlier waiting request for the same lock on the Inserter side.
        Please apply both apars(PM80714 & PM88519) to avoid the problem.
    COMPONENT:  5695-16401-HIR2230
    APARS FIXED: PM88519
    SPECIAL CONDITIONS:
      COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DXRRL7B1  PM88519

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88519   DXRRL7B1

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DXRRL7B1

      LISTEND
 UK95009 COVER LETTER END


 UK95026 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86960 -
        ****************************************************************
        * USERS AFFECTED: DB2 10 for z/OS users of statement-level     *
1       *                 optimization hints                           *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00E70005 at the location     *
        *                      DSNXOGP M978 may occur when binding a   *
        *                      package or a plan with a query which    *
        *                      could match a statement-level           *
        *                      optimization hint but the hint is       *
        *                      invalid.                                *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        ABEND04E RC00E70005 at the location DSNXOGP M978 may occur when
        binding a package or a plan with a query which could match a
        statement-level optimization hint, and the hint is invalid
        for either of the following reasons:

        1. Access path information for a correlated subquery is missing
        in the hint; OR

        2. Access path information for parallelism is invalid in the
        hint.

        Additional Keywords:
        ABEND04E RC00E70005 in DSNXOGP M978 OPTHINT OPTHINTS HINTS
        SQLCORRSUBQ SQLSUBQUERY PARALLELISM SQLPARALLELISM DB2PARALL/K
        The code has been modified to invalidate the statement-level
        optimization hints rather than to issue an ABEND for the case
        described as above.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM86960
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM84153:

        See PM84153 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM84153 corrects a problem that incorrect output may occur if
        an ORDER BY expression with DESC is specified in a table
        expression and the table expression is materialized for
        merge scan 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.
      DB2BIND:
        ***Action for PM59833:

        A rebind is necessary for static applications to rebuild
        access paths based on the changes in this APAR.

        PM59833 corrects a problem that DB2 may select an inefficient
        access path for a query with a subquery having multiple-table
1       join when subsystem parameter OPTXQB is ON.

        To make this fix effective for a static application, it must 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 PM55941:

        See PM55941 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM55941 corrects a problem of a query with OPTIMIZE FOR n ROWS
        or FETCH FIRST n ROWS ONLY where DB2 chooses the
        non-correlated subquery access path instead of the
        correlated subquery access path.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        See PM53285 APAR/PTF text in the PTF cover letter for
        additional information about why a REBIND is necessary.

        PM53285 fixes an execution time abend when a query contains a
        user-defined function and is run in parallelism.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOCS   PM86960
       DSNXOLL   PM86960
       DSNXOPCO  PM86960

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM86960   DSNXOCS  DSNXOLL  DSNXOPCO

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOCS
       DSNXOLL
       DSNXOPCO

      LISTEND
 UK95026 COVER LETTER END


 UK95038 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89692 -
        ****************************************************************
1       * USERS AFFECTED: All users of DB2 for zOS.                    *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00D92023 in DSNRPLCS         *
        *                      during DB2 restart.                     *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        A POSTPONED ABORT unit of recovery (UR) for a thread that
        owned the only UR in a global transaction completed the backout
        process and an END-UNDO log record was written by DSNRPBUP to
        complete the UR.  DSNRPBUP then attempted to remove the GXID
        for the global transaction from the GXID table without holding
        the correct latch to serialize the hash anchor chains.  This
        resulted in the GXID block being left on the GXID chain without
        any URs.  The global transaction information for the orphaned
        GXID was written to the log during the subsequent checkpoints.
        The next restart then failed with an ABEND04E RC00D92023 in
        DSNRPLCS as no URs were found for the checkpointed global
        transaction.  A conditional restart specifying a CHKPTRBA
        prior to the END-UNDO log record RBA was required to restart
        DB2.
        DSNRPBUP has been changed to obtain the GXID latch when
        removing a completed GXID block from the GXID table.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89692
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNRPBUP  PM89692

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89692   DSNRPBUP

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNRPBUP

      LISTEND
 UK95038 COVER LETTER END


 UK95040 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86674 -
        ****************************************************************
        * USERS AFFECTED: DB2 9 and 10 for z/OS users of XML           *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00E70005 at location         *
        *                      DSNNXML.DSNNSISC M100 upon INSERT       *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        ABEND04E RC00E70005 DSNNXML.DSNNSISC M100 may occur when DB2 is
1       attempting to insert a new string id row into the
        SYSIBM.SYSXMLSTRINGS table upon DML or LOAD into a table,
        but during internal processing the DSNDB06.SYSINDEXES table
        space is not available. DB2 needs to return a -904 SQLCODE for
        the resource unavailable case instead of producing the abend.
        DB2 code is now fixed to issue SQLCODE -904 indicating resource
        not available.

        Additional Keywords:
        SQLINSERT SQLCODE904 SQLXML XMLALL
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM86674
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNNSISC  PM86674

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM86674   DSNNSISC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNNSISC

      LISTEND
 UK95040 COVER LETTER END


 UK95042 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM84665 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users who use  *
        *                 the CREATE TRIGGER statement.                *
        ****************************************************************
        * PROBLEM DESCRIPTION: SQLCODE206 or SQLCODE203 may occur for  *
        *                      a CREATE TRIGGER statement where the    *
        *                      trigger subject table is also refe-     *
        *                      renced in a scalar full select in the   *
        *                      trigger body.                           *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Here is an example to show the failing case.

         =========
          EXAMPLE
         =========

         CREATE TABLE MYTB (NUM INT);

         CREATE TRIGGER MYTG NO CASCADE BEFORE INSERT ON MYTB
             REFERENCING NEW AS NROW
1            FOR EACH ROW MODE DB2SQL
             BEGIN ATOMIC
             SET NROW.NUM = (SELECT MAX(A.NUM) + 1
                               FROM MYTB A);
             END!

        DB2 code has been modified to handle the aforementioned problem
        for CREATE TRIGGER correctly.

        Additional keywords: SQLTRIGGER SQLSCALAR SQLFULLSELECT
                             SQLSCALARFULSEL SQLCODE206 SQLCODE203

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM84665
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXORSO  PM84665

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM84665   DSNXORSO

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXORSO

      LISTEND
 UK95042 COVER LETTER END


 UK95045 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM87940 -
        ****************************************************************
        * USERS AFFECTED: All IRLM220 (HIR2220) and IRLM230 (HIR2230)  *
        *                 users.                                       *
        ****************************************************************
        * PROBLEM DESCRIPTION: IRLM Modify STATUS commands may result  *
        *                      in Abend378-18 when SYSx.PARMLIB DIAGxx *
        *                      IGVUNCOND trap is active.               *
        ****************************************************************
        * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
        ****************************************************************
        When IRLM Modify STATUS command is issued, IRLM obtains
        storage for the command output display. This storage is
        a GETMAIN branch entry call from DXRRL2B0. At the end of
        the display, IRLM releases this storage calling FREEMAIN,
        an SVC call from DXRRL0B0 which fails due to incorrect
        parameters. IRLM private storage piece obtained for the
        status command display, gets orphaned as a result.  Also,
        if MVS trap IGVUNCOND is active, it will result in
        ABEND378-18 on the FREEMAIN failure.

1       GEN:
        KEYWORDS:

        *** END IMS KEYWORDS ***
          The FREEMAIN for the STSD block in DXRRL0B0 is changed to use
        BRANCH=YES to be consistent with the GETMAIN in DXRRL2B0.
    COMPONENT:  5695-16401-HIR2230
    APARS FIXED: PM87940
    SPECIAL CONDITIONS:
      COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DXRRL0B0  PM87940

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM87940   DXRRL0B0

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DXRRL0B0

      LISTEND
 UK95045 COVER LETTER END


 UK95047 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86043 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 for z/OS who use IBM DB2    *
        *                 Analytics Accelerator (IDAA).                *
        ****************************************************************
        * PROBLEM DESCRIPTION: A START ACCEL command may result in     *
        *                      abend 04E-00E50001. Specific known      *
        *                      symptoms include:                       *
        *                      . 04E-00E50001 DSNIPPHO+0E26            *
        *                      . 04E-00E50001 DSNIOST2+12B2            *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        START ACCEL command processing involves obtaining a latch
        and then accessing DB2 catalog tables which may require
        conflicting latches.

        DB2 has been changed to maintain proper latch hierarchy during
        START ACCEL command processing.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM86043
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNLDALB  PM86043
1      DSNLTGBK  PM86043
       DSNLTSET  PM86043
       DSNX8CDA  PM86043
       DSNX8INI  PM86043
       DSNX8STA  PM86043
       DSNX8STO  PM86043

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM86043   DSNLDALB DSNLTGBK DSNLTSET DSNX8CDA DSNX8INI DSNX8STA
                 DSNX8STO

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNLDALB
       DSNLTGBK
       DSNLTSET
       DSNX8CDA
       DSNX8INI
       DSNX8STA
       DSNX8STO

      LISTEND
 UK95047 COVER LETTER END


 UK95057 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM83315 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 and 10 for z/OS.                   *
        ****************************************************************
        * PROBLEM DESCRIPTION: IFCIDs may be created with incorrect    *
        *                      values in the correlation header        *
        *                      (QWHC).                                 *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        There is a condition where an IFCID record could be written
        with incorrect values in a correlation header (DSNDQWHC).
        This occurs when an agent externalizing a record is going
        throught deallocation and has freed the CCB control block.
        Do not write an IFCID records for agents that have freed their
        CCB.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM83315
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNWVCOL  PM83315

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM83315   DSNWVCOL

1     THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNWVCOL

      LISTEND
 UK95057 COVER LETTER END


 UK95082 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89112 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS V10 users of query          *
        *                 containing CTE and sparse index              *
        *                 access is chosen.                            *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C90101 at DSNIIMSI:5008    *
        *                      may occur for query containing CTE and  *
        *                      sparse index access is chosen for CTE   *
        *                      table.                                  *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        ABEND04E RC00C90101 at DSNIIMSI:5008 may occur for query
        containing CTE and sparse index access is chosen for CTE table.

        The following query is an example of this case.
           WITH CTE1(CX,CZ,CR,CY, CE) AS
             (SELECT  T1.C2, T1.C5,'','' , T1.C1  FROM T1)

           SELECT T1.C1 , T1.C2 , A.CZ, A.CY FROM T1, CTE1 A
           WHERE T1.C1 = 1 AND T1.C2=A.CZ  AND T1.C3='AAA'
                AND EXISTS (SELECT 1 FROM CTE1 V);
        SOLUTION:
        The bindtime code in DB2 is modified to correct the conditions
        leading to the incorrect result.

        Additional Keywords: SQLCTE SQLSPARSEINDEX
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89112
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        See PM89112 APAR/PTF text in the PTF cover letter for
        additional information about why a REBIND is necessary.

        APAR PM89112 corrects a problem that can cause an abend at
        DSNIIMSI:5008 for a query containing CTE.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
1       ***Action for PM79464:

        See PM79464 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM79464 corrects a problem of ABEND04E RC00E70005 DSNXOSR:P014
        when a query has one miniplan with PARALLELISM ON and MERGC =
        YES and SORTN_JOIN = YES and PRIMARY_ACCESSTYPE = 'T' and the
        query has a GROUP BY clause.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOSR   PM89112
       DSNXO1S   PM89112

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89112   DSNXOSR  DSNXO1S

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOSR
       DSNXO1S

      LISTEND
 UK95082 COVER LETTER END


 UK95094 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86962 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 10 for z/OS who have        *
        *                 queries using OUTER JOIN                     *
        ****************************************************************
        * PROBLEM DESCRIPTION: SQL code -670 with SQLERRD1 = -97 in    *
        *                      accompanying message DSNT416I           *
        *                      may be issued from DSNXOPCO for a       *
        *                      query using OUTER JOIN even if          *
        *                      the row length of the join result       *
        *                      is under the maximum limit.             *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        SQL code -670 and accompanying message DSNT416I with
        SQLERRD1 = -97 from DSNXOPCO may be issued for a query using
        OUTER JOIN even if the row length of the join result is
        under the maximum limit.  This can occur when the same
        column is referred to multiple times in a query.  A
        calculation of the row length of the join result
        incorrectly added the column length of the same column
        multiple times when determining whether to issue the
1       -670 SQL code.  This miscalculation could cause -670
        to be issued erroneously.

        Additional Keywords:
        SQLOUTERJOIN SQLFULLJOIN SQLOUTER SQLFULL SQLJOIN
        SQLLEFTJOIN SQLLEFT SQLRIGHTJOIN SQLRIGHT
        SQLCODE670 MSGDSNT416I
        Code was added to correct the calculation of the join result
        row length when the query contains OUTER JOIN so that SQL
        code -670 can be issued accurately.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM86962
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOPCO  PM86962

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM86962   DSNXOPCO

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOPCO

      LISTEND
 UK95094 COVER LETTER END


 UK95131 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89162 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of REORG with the  *
        *                 Change Data Capture (CDC) attribute for the  *
        *                 catalog table SYSIBM.SYSTABLES.              *
        ****************************************************************
        * PROBLEM DESCRIPTION: A REORG utility updated the data        *
        *                      version into the catalog table SYSIBM.  *
        *                      SYSTABLES, but the log records of these *
        *                      updates were not marked as DATA CAPTURE *
        *                      when this catalog table had the CDC     *
        *                      attribute.                              *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available.         *
        ****************************************************************
        The catalog table SYSIBM.SYSTABLES had the CDC attribute.  A
        REORG TABLESPACE ran on a multi-table table space and updated
        the data versions of the tables into SYSIBM.SYSTABLES.  These
        updates were not logged as DATA CAPTURE.
        The code has been modified to log the data version updates into
        SYSIBM.SYSTABLES during a REORG if this catalog table has the
        CDC attribute.
    COMPONENT:  5740-XYR00-HDBAA10
1   APARS FIXED: PM89162
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUGPAM  PM89162
       DSNUGUVR  PM89162

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89162   DSNUGPAM DSNUGUVR

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUGPAM
       DSNUGUVR

      LISTEND
 UK95131 COVER LETTER END


 UK95132 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89461 -
        ****************************************************************
        * USERS AFFECTED: All DB2 users of dynamic statement caching,  *
        *                 bind options REOPT(ONCE), and DDL statements *
        ****************************************************************
        * PROBLEM DESCRIPTION: When running a dynamic SQL with         *
        *                      dynamic statement caching active        *
        *                      and index probing is used for a         *
        *                      query, S DBD lock is held which blocks  *
        *                      any DDL statement on the same DBD.      *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When a dynamic SQL was being
        issued from applications bound with
        REOPT ( ONCE ) and index probing is
        used for a query, S DBD lock was
        incorrectly acquired.
        DB2 code has been changed to not obtain a DBD
        lock during a DESCRIBE PREPARE when dynamic
        statement caching is active, REOPT(ONCE)
        is used and index probing is used for the
        query.

        Additional search keywords: DYNAMICSQLCACHE
                                    SQLDYNSTMTCACHE
                                    SQLCACHE
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89461
    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
       DSNIBCTD  PM89461
       DSNKCEST  PM89461
       DSNXORTS  PM89461

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89461   DSNIBCTD DSNKCEST DSNXORTS

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIBCTD
       DSNKCEST
       DSNXORTS

      LISTEND
 UK95132 COVER LETTER END


 UK95141 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM81247 -
        ****************************************************************
        * USERS AFFECTED: DB2 10 for z/OS users exploiting the         *
        *                 new EXPLAIN privilege.                       *
        ****************************************************************
        * PROBLEM DESCRIPTION: When a user with EXPLAIN privilege      *
        *                      tried to execute a statement that he    *
        *                      is not authorized to, received          *
        *                      warning message +4726 during prepare    *
        *                      along with SQLCODE -514 at execution    *
        *                      instead of authorization error          *
        *                      SQLCODE -551.                           *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        DB2 10 for z/OS introduced explain privilege which allows users
        to explain and describe the statements without the ability to
        execute the statement. When a user with EXPLAIN privilege tried
        to execute such a statement, received warning message +4726
        during prepare followed by SQLCODE -514 at execution instead
        of authorization error SQLCODE -551.

        The SQLCODE code -518 might also be received in the above
        scenario.
        The negative SQL codes received in this scenario do not indicate
        the authorization error.
        DB2 code has been updated to issue SQLCODE -551 instead of
        -514 or -518 in the above described scenarios.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM81247
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DOCUMENTATION:
1       ***Documentation for PM81247:
        See UK95141 HOLD data for additional information.

        In DB2 10 for z/OS, a user with EXPLAIN privilege, running an
        application attempting to execute an SQL statement that he does
        not have authority to execute will receive warning message with
        SQLCODE +4726, SQLSTATE 0168Z followed by SQLCODE -551, SQLSTATE
        42501 instead of SQLCODE -514 or SQLCODE -518.

        The documentation for following SQL codes are updated to remove
        the reference to EXPLAIN privilege from SQLCODE -514 and -518
        as below:

        -514:
        THE CURSOR cursor-name IS NOT IN A PREPARED STATE

        Explanation:
        The application program has tried to use a cursor, 'cursor-name'
        that is not in a prepared state.
        The cursor is associated with a statement that:
        1. Was never prepared.
        2. Was invalidated by a commit or rollback operations

        System action:
        The statement cannot be processed.

        Programmer response:
        For case 1, ensure that you prepare the statement that is named
        in the DECLARE CURSOR statement for 'cursor-name' before you
        try to open the cursor.
        For case 2, take one of the following actions:
         - Use the WITH HOLD option of DECLARE CURSOR.
         - Do not execute a commit or rollback operation until you are
           finished using the cursor.
         - Prepare the statement again after the commit or rollback.

        SQLSTATE
        26501

        -518:
        THE EXECUTE STATEMENT DOES NOT IDENTIFY A VALID PREPARED
        STATEMENT.

        Explanation:
        One of the following conditions exists:
         - The statement identified in the EXECUTE statement has not
           been prepared.
         - The statement identified in the EXECUTE statement identifies
           a SELECT, or ASSOCIATE LOCATORS statement.
         - The statement identified in the EXECUTE IMMEDIATE statement
           identifies a SELECT or ASSOCIATE LOCATORS statement.

        System action:
        The statement cannot be processed.

        Programmer response:
1       Ensure that you prepare the statement prior to EXECUTE. Also,
        ensure that the statement prepared is not:
         - A SELECT statement.
         - An ASSOCIATE LOCATORS statement.

        SQLSTATE
        07003
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXECL   PM81247
       DSNXECLF  PM81247
       DSNXECLN  PM81247
       DSNXECW   PM81247
       DSNXECWA  PM81247
       DSNXECWU  PM81247
       DSNXEDP   PM81247
       DSNXERT2  PM81247
       DSNXOCF   PM81247
       DSNXODML  PM81247
       DSNXOIN   PM81247
       DSNXOMRG  PM81247
       DSNXOOP   PM81247
       DSNXORFN  PM81247
       DSNXOSC   PM81247
       DSNXOSEQ  PM81247
       DSNXOST   PM81247
       DSNXOSTP  PM81247

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM81247   DSNXECL  DSNXECLF DSNXECLN DSNXECW  DSNXECWA DSNXECWU
                 DSNXEDP  DSNXERT2 DSNXOCF  DSNXODML DSNXOIN  DSNXOMRG
                 DSNXOOP  DSNXORFN DSNXOSC  DSNXOSEQ DSNXOST  DSNXOSTP

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXECL
       DSNXECLF
       DSNXECLN
       DSNXECW
       DSNXECWA
       DSNXECWU
       DSNXEDP
       DSNXERT2
       DSNXOCF
       DSNXODML
       DSNXOIN
       DSNXOMRG
       DSNXOOP
       DSNXORFN
       DSNXOSC
       DSNXOSEQ
       DSNXOST
       DSNXOSTP

      LISTEND
1UK95141 COVER LETTER END


 UK95142 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM87403 -
        ****************************************************************
        * USERS AFFECTED: DB2 9 and DB2 10 for z/OS users using        *
        *                 indexes.                                     *
        ****************************************************************
        * PROBLEM DESCRIPTION: <1>REORG TABLESPACE utility SHRLEVEL    *
        *                      REFERENCE or SHRLEVEL CHANGE by PART    *
        *                      with nonpartitioned secondary indexes   *
        *                      (NPSIs) defined on the table            *
        *                      executes with long elapsed time.        *
        *                                                              *
        *                      <2>LOAD utility RESUME YES on the       *
        *                      table with indexes defined executes     *
        *                      with long elapsed time.                 *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When running the following utilities:
        <1>REORG TABLESPACE utility SHRLEVEL REFERENCE or SHRLEVEL
           CHANGE by PART with nonpartitioned secondary indexes (NPSIs)
           defined on the table
        <2>LOAD utility RESUME YES on the table with indexes defined
        If there are many space map pages in the indexes,
        the utility operation could take a long time to finish.
        This is caused by the exhaustive index space map page search
        when allocating new index pages during the utility operation.
        Index manager code has been changed to reduce the number of
        index space map page exhaustive searches during the following
        utility operations:
        <1>REORG TABLESPACE utility SHRLEVEL REFERENCE
           or SHRLEVEL CHANGE by PART
        <2>LOAD utility RESUME YES
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM87403
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNKIXDB  PM87403
       DSNKSALO  PM87403

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM87403   DSNKIXDB DSNKSALO

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNKIXDB
       DSNKSALO

1     LISTEND
 UK95142 COVER LETTER END


 UK95148 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86044 -
        ****************************************************************
        * USERS AFFECTED: DB2 10 for z/OS users of optimization hints  *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00E70005 at the location     *
        *                      DSNXOHJC P005 may occur when binding    *
        *                      a package or a plan with a query which  *
        *                      uses an optimization hint if the        *
        *                      following conditions are satisfied:     *
        *                      1. The hint specifies SORTC_JOIN='Y',   *
        *                      ACCESSTYPE='N' and METHOD=1 for the     *
        *                      inner table of a join;                  *
        *                      2. The index specified for the inner    *
        *                      table in the hint contains a column     *
        *                      which can be matching on an equal join  *
        *                      predicate and a local IN-list           *
        *                      predicate.                              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        ABEND04E RC00E70005 at the location DSNXOHJC P005 may occur when
        binding a package or a plan with a query which uses an
        optimization hint if the following conditions are satisfied:

        1. The hint specifies SORTC_JOIN = 'Y', ACCESSTYPE = 'N' and
        METHOD = 1 (nested loop join) for the inner table of a join;

        2. The index specified for the inner table in the hint contains
        a column which can be matching on an equal join predicate and
        a local IN-list predicate.

        For example,
        SELECT *
        FROM T1, T2
        WHERE T1.C1 = T2.C1
          AND T2.C1 IN (1,2,3)

        There is an index IX1 defined on T2(C1). If the hint specifies
        the join sequence for the above query is from T1 to T2, IX1 is
        the index used to access the table T2, and SORTC_JOIN='Y',
        ACCESS_TYPE='N' and METHOD=1 are specified for the table T2 in
        the hint, then DB2 will use T2.C1 IN (1,2,3) as the matching
        predicate. However, DB2 cannot support a local predicate as the
        matching predicate if the composite table has been sorted and
        the local predicate references a join column, which could lead
        to an ABEND.

        The problem could also occur if the bind option APREUSE(ERROR)
        is used and the access path chosen in the prior BIND/REBIND
        satisfies the conditions described as above.
1
        Additional Keywords:
        ABEND04E RC00E70005 in DSNXOHJC P005 OPTHINT SQLHINT SQLNLJ
        APREUSE
        Code has been modified to select the equal join predicate as
        the matching predicate for the case described as above to avoid
        the ABEND.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM86044
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM84178:

        A rebind is necessary for static applications to rebuild
        access paths based on the changes in this APAR.

        PM84178 corrects a problem of poor performance of a query if the
        query selects an index which matches multiple IN-subquery
        predicates and there are many records qualified from these
        subqueries.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM69269:

        See PM69269 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM69269 corrects a problem of allowing page range in some cases
        when using optimization hints where page range would not be
        allowed if hints were not used.

        To make this fix effective for a static application, it must 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 PM65757:

        See PM65757 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM65757 corrects a problem that an ABEND04E RC00E70005 in
        DSNXOBM P030 may occur or incorrect output may be produced if
        an optimization hint is used.

        To make this fix effective for a static application, it must 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
       DSNXOGBM  PM86044
       DSNXOPTH  PM86044

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM86044   DSNXOGBM DSNXOPTH

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOGBM
       DSNXOPTH

      LISTEND
 UK95148 COVER LETTER END


 UK95172 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM87899 -
        ****************************************************************
        * USERS AFFECTED: All Users of DB2.                            *
        ****************************************************************
        * PROBLEM DESCRIPTION: Message DSNT408I with SQLCODE = -911    *
        *                      and RC00C20264 during SELECT, after     *
        *                      Postponed Unit of Work recovery.        *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        After the recovery of postpone Abort (PA) objects, it is
        possible that not all partitions of the partition object are
        available to the new application, although data recovery is
        completed successfully. This is because Data Manager's (DM) log
        apply logic for postponed abort URs does not resets a flag in
        Page set Block (PB) to indicate that the partition is now open
        for P-lock negotiation. This results in application may fail
        with reason code RC00C20264 or SQLCODE -911 when selecting from
        partition objects involved in postponed abort recovery.
        DB2 restart logic is changed to avoid application failure with
        SQLCODE -911 after successful recovery of postpone abort
        objects.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM87899
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNIARPL  PM87899

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM87899   DSNIARPL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
1      DSNIARPL

      LISTEND
 UK95172 COVER LETTER END


 UK95190 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM80868 -
        ****************************************************************
        * 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 symptoms   *
        *                      occurs when running job DSNTIJRV, job   *
        *                      step DSNTRVFY (program DSNTRVFY):       *
        *                                                              *
        *                      (1) DSNTRVFY terminates with return     *
        *                          code 12 and this message:           *
        *                            DSNT035I DSNTRVFY VALIDATION      *
        *                            PROGRAM FAILED TO INITIALIZE,     *
        *                            REASON CODE = 04                  *
        *                          when more than one instance is      *
        *                          executed at the same time, i.e.     *
        *                          DSNTRVFY is executed when the       *
        *                          DSNTRVFY console is already active. *
        *                      (2) DSNTRVFY validates routine          *
        *                          SYSPROC.ADMIN_TASK_ADD successfully *
        *                          but the following message appears   *
        *                          in the SYSOUT DD output of the DB2  *
        *                          administrative task scheduler       *
        *                          (DSNAMDT0):                         *
        *                            passwd: EDC5121I Invalid          *
        *                            argument. (errno2=0x090C02A6)     *
        *                      (3) DSNTRVFY terminates with return     *
        *                          code 8 and this message:            *
        *                            DSNT002I DSNTRVFY RECEIVED AN     *
        *                            UNEXPECTED SQLCODE OF -20212      *
        *                            FROM THE CALL PROCEDURE REQUEST   *
        *                          from the validation of routine      *
        *                          SYSPROC.XSR_COMPLETE when the       *
        *                          default EBCDIC CCSID setting for    *
        *                          DB2 is a character set such as      *
        *                          SCCSID=290/MCCSID=930 which does    *
        *                          not locate the lowercase Latin      *
        *                          character set at the same code      *
        *                          points as CCSID 37 (US English).    *
        ****************************************************************
        * RECOMMENDATION: Apply the fixing PTF for this APAR.          *
        ****************************************************************
        This APAR addresses the following problems with installation
        job DSNTIJRV, program DSNTRVFY (the validation program for
        DB2-supplied routines):
1
        (1) If more than one instance of DSNTRVFY executes at the same
            time, some instances can terminate with return code 12 due
            to message
              DSNT035I DSNTRVFY VALIDATION PROGRAM FAILED TO INITIALIZE,
                       REASON CODE = 04
            This error indicates that the extended MCS console for
            DSNTRVFY could not be activated.  There can only be one
            active DSNTRVFY console at a given time.

        (2) The following message appears in the SYSOUT DD output of the
            DB2 administrative task scheduler (DSNAMDT0) during
            validation of the SYSPROC.ADMIN_TASK_ADD stored procedure:
              passwd: EDC5121I Invalid argument. (errno2=0x090C02A6)
            This message indicates that the z/OS System Authorization
            Facility (SAF) received an invalid argument for a password.
            It is an unintended side affect of the call format used by
            DSNTVRFY to validate SYSPROC.ADMIN_TASK_ADD.

        (3) If DB2's default EBCDIC CCSID setting is a character set
            such as SCCSID=290/MCCSID=930 which locates the lowercase
            Latin characters at different code points than the US
            English CCSID 37, DSNTRVFY terminates with return code 8 due
            to message
              DSNT002I DSNTRVFY RECEIVED AN
              UNEXPECTED SQLCODE OF -20212
              FROM THE CALL PROCEDURE REQUEST
            during validation of SYSPROC.XSR_COMPLETE.  The error
            occurs because the Java class path name cannot be
            interpreted correctly.

        In response, DSNTRVFY is modified as follows:
        (1) When the request to activate the DSNTRVFY extended MCS
            console fails because another instance has it in use,
            DSNTRVFY will retry the request every 30 seconds for up
            to 30 minutes.  A note has been added to the DSNTIJRV job
            prolog to document this behavior.

        (2) Validation of SYSPROC.ADMIN_TASK_ADD is modified to prevent
            triggering messages from the z/OS System Authorization
            Facility that appear in the DB2 administrative scheduler
            task log.

        (3) Self-binding of DSNTRVFY's package and plan is modified
            to use CCSID(1047) to ensure that the Java class path
            name for SYSPROC.XSR_COMPLETE is interpreted correctly
            regardless of DB2's default EBCDIC CCSID setting.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM80868
    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  PM80868
       DSNTIJRV  PM80868
1      DSNTRVFY  PM80868

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM80868   DSN@RVFY DSNTIJRV DSNTRVFY

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNTRVFY

      MACROS
       DSN@RVFY
       DSNTIJRV

      LISTEND
 UK95190 COVER LETTER END


 UK95238 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM87864 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 stored procedures that:     *
        *                 1. Declare and open a WITH HOLD cursor       *
        *                    inside the stored procedure               *
        *                 2. Specify to accelerate the query           *
        *                 3. Call the stored procedure remotely        *
        ****************************************************************
        * PROBLEM DESCRIPTION: SQLCODE518 is received on FETCH         *
        *                      after a COMMIT inside stored            *
        *                      procedure for accelerated query         *
        *                      when the CURSOR is OPEN and             *
        *                      declared WITH HOLD.                     *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        In the case of accelerated query inside remote stored
        procedure, the WITH HOLD attribute is not passed over
        and upon OPEN, the attribute is reset and the cursor
        is closed during COMMIT.
        The WITH HOLD attribute is passed during OPEN of cursor for
        accelerated query in remote stored procedure call.

        additional keywords:
         SQLSP SQLSTOREDPROC IDAAV2R1/K IDAAV3R1/K
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM87864
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNLXROP  PM87864
       DSNXEPM   PM87864

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1      PM87864   DSNLXROP DSNXEPM

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNLXROP
       DSNXEPM

      LISTEND
 UK95238 COVER LETTER END


 UK95240 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90486 -
        ****************************************************************
        * USERS AFFECTED: All DB2 users.                               *
        ****************************************************************
        * PROBLEM DESCRIPTION: AE PM85944 FIX COMPLETION               *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        AE PM85944 FIX COMPLETION
        AE PM85944 FIX COMPLETION
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM90486
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNB1DVP  PM90486
       DSNB1FBS  PM90486

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90486   DSNB1DVP DSNB1FBS

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNB1ABS
       DSNB1CPS
       DSNB1DVP
       DSNB1FBS
       DSNB1PMT

      LISTEND
 UK95240 COVER LETTER END


 UK95251 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM87648 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of an SQL          *
        *                 statement that contains a user defined       *
1       *                 function with a LOB locator parameter.       *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00E70005 at the location     *
        *                      DSNXGRDS DSNXGUDF M105 could happen for *
        *                      an SQL statement that contains a user   *
        *                      defined function with a LOB locator     *
        *                      parameter.                              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An example is shown below:

        CREATE FUNCTION MYFUN(MYDOC CLOB(2G) AS LOCATOR)
          RETURNS VARCHAR(10)
          LANGUAGE C
          EXTERNAL NAME MYFUN
          PARAMETER STYLE DB2SQL
          PARAMETER CCSID EBCDIC
          PARAMETER VARCHAR NULTERM
          PROGRAM TYPE SUB
          SCRATCHPAD 1000
          FINAL CALL
          FENCED
          NOT DETERMINISTIC
          EXTERNAL ACTION
          DBINFO
          DISALLOW PARALLEL
          RUN OPTIONS 'POSIX(ON),XPLINK(ON)'
          WLM ENVIRONMENT WLMENV3;

        SELECT * FROM
        SYSIBM.SYSDUMMY1
        WHERE MYFUN(CLOB('LOBLOC')) = 'A';

        DB2 did not correctly process the aforementioned SQL statements,
        which caused the ABEND.
        DB2 has been modified to correctly process the aforementioned
        SQL statement, so there will be no ABEND.

        Additional keywords: SQLUDF SQLLOB
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM87648
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOEXI  PM87648

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM87648   DSNXOEXI

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOEXI
1
      LISTEND
 UK95251 COVER LETTER END


 UK95252 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM81500 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users          *
        *                 of queries containing predicates.            *
        ****************************************************************
        * PROBLEM DESCRIPTION: Improper SQL error processing can occur *
        *                      for a query involving predicates when   *
        *                      the query is being executed             *
        *                      sequentially.  If the query is executed *
        *                      with parallelism, a loop can occur.     *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Improper SQL error processing can occur for a query involving
        predicates.

        When DB2 is processing a query with predicates and an SQLCODE
        -330 (SQLCODE330) or -332 (SQLCODE332) error is expected, the
        error message may not be properly formatted when the query is
        running sequentially.  Additionally, if the query is executed
        with parallelism, a loop can occur.

        There are many reasons that DB2 will issue an SQLCODE -330 or
        -332.  One scenario is when converting a UNICODE string into an
        EBCDIC string and the resulting string is not a valid EBCDIC
        string.  In this case, DB2 is supposed to issue an SQLCODE.
        But, due to the processing error, no SQLCODE is formatted for
        certain cases.
        The code in DB2 has been modified to process SQL errors
        properly so that the error will be externalized as expected.
        So, the correct SQL code will be issued which will prevent the
        incorrect result from being returned for the sequential case or
        the looping condition for the parallel case.

        Additional Keywords: SQLCODE330 SQLCODE332
                             SQLINCORR SQLINCORROUT INCORROUT
                             DB2INCORR/K DB2PARALL/K
                             PARALLELISM SQLPARALLELISM

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM81500
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXRFC   PM81500
       DSNXRFC9  PM81500

1     CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM81500   DSNXRFC  DSNXRFC9

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXRFC
       DSNXRFC9

      LISTEND
 UK95252 COVER LETTER END


 UK95255 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86502 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of predicates with *
        *                 a double floating point column being         *
        *                 compared to a decimal floating point         *
        *                 constant.                                    *
        ****************************************************************
        * PROBLEM DESCRIPTION: An ABEND04E RC00E70005 can occur at     *
        *                      location DSNXGRDS DSNXRFC P106 for an   *
        *                      SQL statement containing a predicate    *
        *                      that compares a double floating point   *
        *                      column to a decimal floating point      *
        *                      constant.                               *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An ABEND04E RC00E70005 can occur at location DSNXRFC offset P106
        for a query that contains a predicate which compares a double
        floating point column to a constant that is a decimal floating
        point number.  The problem can occur when precision is lost when
        converting the constant to a DOUBLE data type.

        The following example illustrates how this problem can occur.

        1. Create a table with a column defined as a DOUBLE data type.

          CREATE TABLE TEST (C1 DOUBLE);
          INSERT INTO TEST VALUES (1.11111111111111);

        2. Execute the following query.

          SELECT * FROM TEST
          WHERE C1 >= DECFLOAT('013021100000023001')


        DB2 should retrieve the inserted data when executing the query.
        However, the above ABEND occurs because DB2 did not handle
        converting the decfloat constant correctly.

        DB2 has been modified to convert the decfloat constant correctly
        to a double floating point number which will allow the predicate
1       comparison to work properly.

        Additional Keywords : SQLDECFLOAT SQLDOUBLE SQLDECIMAL SQLFLOAT
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM86502
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXRFC   PM86502

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM86502   DSNXRFC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXRFC

      LISTEND
 UK95255 COVER LETTER END


 UK95264 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88763 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users who rebind         *
        *                 DB2 9 for z/OS packages of Native SQL        *
        *                 procedure which contains timestamp           *
        *                 data type sql variable.                      *
        ****************************************************************
        * PROBLEM DESCRIPTION: An ABEND04E RC00E70005 in               *
        *                      DSNXGRDS DSNXRTIM P008 could occur      *
        *                      when running a Native SQL procedure     *
        *                      which satisfies the following           *
        *                      conditions:                             *
        *                      1. It is created in DB2 9 for z/OS,     *
        *                      2. It contains timestamp data type      *
        *                         SQL variable,                        *
        *                      3. It is rebound in DB2 10 for z/OS.    *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The following example could recreate the Abend,

        CREATE TABLE T1(C1 VARCHAR(30)) ?
        CREATE PROCEDURE MYTEST1
          BEGIN
            DECLARE VAR1 TIMESTAMP;
            SET VAR1 = CURRENT TIMESTAMP;
            INSERT INTO T1 VALUES(VAR1);
          END?

        DB2 doesn't rebind the above native SQL procedure correctly
1       which causes abend during execution of the procedure.
        DB2 is updated to rebind DB2 9 for z/OS Native SQL procedure
        in DB2 10 for z/OS correctly.
        Additional Keywords: SQLNATIVESQLPL SQLTIMESTAMP SQLREBIND
                             SQLPROCEDURE
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88763
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM88763:

        See PM88763 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM88763 corrects a problem of an ABEND04E RC00E70005 in
        DSNXGRDS.DSNXRTIM:P008 occured when running a Native SQL
        procedure which contains timestamp data type SQL variable,
        this procedure is created in DB2 9 for z/OS, rebound in DB2
        10 for z/OS.

        To make this fix effective for a static application, it must 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
       DSNXODTR  PM88763
       DSNXOTF   PM88763

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88763   DSNXODTR DSNXOTF

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXODTR
       DSNXOTF

      LISTEND
 UK95264 COVER LETTER END


 UK95265 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM87185 -
        ****************************************************************
        * USERS AFFECTED: DB2 users.                                   *
        ****************************************************************
        * PROBLEM DESCRIPTION: Threads suspended in DSNB1TMR.          *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Due to a failure by the timer service task's STIMER exit to post
        the waiting task, outstanding timer requests, as well as new
1       ones coming in, never got resumed.
        A correction was made to the timer service task's STIMER exit,
        to properly handle being driven in 64-bit mode.  Additionally,
        code was added to have a new timer request wake up the service
        task if the oldest request is overdue, to allow it to recover
        from a failure to be posted by the exit.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM87185
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNB1TMR  PM87185

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM87185   DSNB1TMR

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNB1TMR

      LISTEND
 UK95265 COVER LETTER END


 UK95271 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM87560 -
        ****************************************************************
        * USERS AFFECTED: DB2 data sharing users.                      *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND026 in IXLE1CRW after a buffer     *
        *                      pool has had its VPSIZE reduced, either *
        *                      due to the buffer pool having the       *
        *                      AUTOSIZE attribute set to YES, or by    *
        *                      use of the -ALT BPOOL VPSIZE command.   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        If a buffer pool has its size reduced, and it is connected to
        the Group Buffer Pool, DB2 may reduce the size of the pool's
        Local Valid Bit Vector to reflect the new highest used slot
        number.  However, the pool contraction logic may fail to
        deregister pages using higher slot numbers.  If that happens,
        and a later cross-invalidation request is sent for one of
        those still-registered pages, an ABEND026 in IXLE1CRW may
        occur due to the use of an invalid vector index.
        The buffer pool contraction logic has been modified to ensure
        that pages being contracted out of the pool are properly
        deregistered.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM87560
    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
       DSNB1CBP  PM87560
       DSNB1FBS  PM87560
       DSNB1REL  PM87560
       DSNB1RWI  PM87560

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM87560   DSNB1CBP DSNB1FBS DSNB1REL DSNB1RWI

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNB1CBP
       DSNB1FBS
       DSNB1REL
       DSNB1RWI

      LISTEND
 UK95271 COVER LETTER END


 UK95283 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88612 -
        ****************************************************************
        * USERS AFFECTED: All users that issue a select from           *
        *                 SYSIBM.SYSLGRNX.                             *
        ****************************************************************
        * PROBLEM DESCRIPTION: SELECT from SYSIBM.SYSLGRNX can         *
        *                      return an sqlstate 01517.               *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        DB2 is running with MIXED=YES and  MCCSID=939 specified in
        DSNHDECP. The following query is executed:

        SELECT LGRDBID, LGRPSID,
               LGRSLRSN, HEX(LGRSLRSN), LGRELRSN, HEX(LGRELRSN)
          FROM SYSIBM.SYSLGRNX
            ORDER BY LGRDBID, LGRPSID, LGRSLRSN;

        This returns an sqlstate of 01517.  Other MCCSIDs may get the
        same failure.
        The following columns in SYSIBM.SYSLGRNX are CHAR FOR BIT

        LGRDBID
        LGRPSID
        LGRSRBA
        LGRSPBA
        LGRSLRSN
        LGRELRSN
        LGRMEMB

        The FOREIGNKEY column in the rows in SYSIBM.SYSCOLUMNS for
1       SYSLGRNX incorrectly has a value of 'S' and this
        could cause the sqlstate 01517 to be returned. The
        FOREIGNKEY column was change to 'B' for these rows to
        correct the problem. The rows will be correctly inserted
        if this apar is on before DSNTIJNF is run for the first
        time or they can be corrected after you are in NFM by
        running the job

        CATMAINT UPDATE UNLDDN PM88612

        ++HOLD for PM88612

        This apar corrects rows for the SYSIBM.SYSLGRNX table in
        SYSIBM.SYSCOLUMNS table.  To verify if the catalog has already
        been updated run the query:

        SELECT * FROM SYSIBM.COLUMNS
          WHERE COL.TBNAME='SYSLGRNX' AND FOREIGNKEY='B'

        The query will return seven rows if the catalog has been updated
        and zero rows if it has not been updated. If the query returns
        zero rows the catalog can be updated by running the utility job

        CATMAINT UPDATE UNLDDN PM88612

        The job will replace any existing catalog rows for directory
        objects that existed before the job is run.  This will
        invalidate packages that are dependent on the directory tables.

        The job is very quick and can be run at any time after applying
        the apar.  Running the job multiple times will not cause any
        problems.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88612
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        ***Action for PM88612:

        This apar corrects rows for the SYSIBM.SYSLGRNX table in
        SYSIBM.SYSCOLUMNS table.  To verify if the catalog has already
        been updated run the query:

        SELECT * FROM SYSIBM.COLUMNS
          WHERE COL.TBNAME='SYSLGRNX' AND FOREIGNKEY='B'

        The query will return seven rows if the catalog has been updated
        and zero rows if it has not been updated. If the query returns
        zero rows the catalog can be updated by running the utility job

        CATMAINT UPDATE UNLDDN PM88612

        The job will replace any existing catalog rows for directory
        objects that existed before the job is run.  This will
        invalidate packages that are dependent on the directory tables.
1
        The job is very quick and can be run at any time after applying
        the apar.  Running the job multiple times will not cause any
        problems.
      ACTION:
        This apar provides the ability to update the catalog to allow
        selects from the directory tables DBDR and SPTR. To verify
        if the catalog has already been updated run the query:

        SELECT * FROM SYSIBM.SYSTABLESPACE
          WHERE DBNAME='DSNDB01' AND NAME='DBD01';

        The query will return one row if the catalog has been updated
        and zero rows if it has not been updated. If the query returns
        zero rows the catalog can be updated by running the utility job

        CATMAINT UPDATE UNLDDN PM80685

        The job will replace any existing catalog rows for directory
        objects that existed before the job is run.  This will
        invalidate packages that are dependent on the directory tables.

        The job is very quick and can be run at any time after applying
        the apar.  Running the job multiple times will not cause any
        problems.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUECM0  PM88612
       DSNUECSE  PM88612

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88612   DSNUECM0 DSNUECSE

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUECM0
       DSNUECSE

      LISTEND
 UK95283 COVER LETTER END


 UK95285 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM85771 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of LOAD utility.   *
        ****************************************************************
        * PROBLEM DESCRIPTION: New option for LOAD to generate unique  *
        *                      value for TIMESTAMP column with default *
        *                      precision when not provided by the user *
        ****************************************************************
        * RECOMMENDATION: Apply PTF when available                     *
        ****************************************************************
        User has a table with a unique index defined on a TIMESTAMP
1       NOT NULL WITH DEFAULT column, and the LOAD utility is used to
        populate this table with LOAD generating the default timestamp
        value for this column at run time as each record is loaded
        (i.e. user does not provide input value for this column in the
        SYSREC input dataset).

        The above scenario would work as long as the rate of the data
        records being loaded is slower than the highest precision of
        the TIMESTAMP value, resulting in a unique timestamp value for
        each record loaded.  However, after user upgrades to the newer
        faster hardware (e.g. EC12), LOAD is running so fast that the
        same store clock value is generated on the TIMESTAMP column of
        consecutive records loaded.  This resulted in a LOAD failure
        due to unique index key violation in the SORTBLD phase.

        Fundamentally, the above issue is caused by the database design
        where non-unique TIMESTAMP values are used as unique keys, and
        this problem could have happened anytime in the past, with the
        hardware upgrade increases the likelihood of its occurrence.
        As an alternative approach, user can define the unique keys on
        higher precision TIMESTAMP column starting in DB2 V10 NFM, or
        define the unique keys using multiple columns to further
        guarantee uniqueness.

        To provide temporary relief for users hitting this issue, a
        new undocumented option is introduced for the LOAD utility to
        ensure uniqueness of generated TIMESTAMP column values on
        consecutively loaded records.  This function is triggered when
        DIAGNOSE TYPE(556) is specified, as in the example below:

        //SYSIN    DD *
           DIAGNOSE TYPE(556)
           LOAD INDDN SYSREC ...

        Note that this uniqueness checking is only applicable to a
        single RELOAD task, so user can still encounter non-unique
        TIMESTAMP values when load partition parallelism is used,
        with or without DIAGNOSE TYPE(556) specified.
        Code has been modified to provide support on the aforementioned
        DIAGNOSE TYPE processing during LOAD execution.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM85771
    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  PM85771
       DSNURWUF  PM85771

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM85771   DSNURWBG DSNURWUF

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
1      DSNURWBG
       DSNURWUF

      LISTEND
 UK95285 COVER LETTER END


 UK95292 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89611 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS and all DB2 10 for z/OS   *
        *                 users of RUNSTATS utility collecting         *
        *                 HISTOGRAM statistics on indexes.             *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00E2002F at DSNSVSFM         *
        *                      OFFSET0794 during HISTOGRAM             *
        *                      statistics collection.                  *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        When the user executed RUNSTATS INDEX LIST HISTOGRAM
        NUMCOLS 10 NUMQUANTILES 100, the utility terminated with
        ABEND04E RC00E2002F at DSNSVSFM + x'0794'

        The abend was caused by not checking the maximum number of
        allocated quantiles before processing the next aggregated
        quantile.
        Code was modified to check for the maximum number of
        allocated quantiles before processing the next quantile.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89611
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUSAH1  PM89611

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89611   DSNUSAH1

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUSAH1

      LISTEND
 UK95292 COVER LETTER END


 UK95295 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88758 -
        ****************************************************************
        * USERS AFFECTED: DB2 V9 data sharing users with UK82634       *
1       *                 applied.                                     *
        *                 DB2 V10 data sharing users with UK82633      *
        *                 or UK93475 applied.                          *
        ****************************************************************
        * PROBLEM DESCRIPTION: Castout I/O errors, as shown by message *
        *                      MSGDSNB225I with CSECT name DSNB5PCO    *
        *                      and MM error code 00140408, along with  *
        *                      ABEND04E RC00C200A4 in DSNB5PCO.        *
        *                                                              *
        *                      Various symptoms of regressed pages,    *
        *                      including:                              *
        *                        - Incorrect output, INCORROUT.        *
        *                        - ABEND04E RC00C90101, RC00C90102,    *
        *                          RC00C90105, or RC00C902xx in        *
        *                          various CSECTs.                     *
        *                        - Data/index inconsistencies reported *
        *                          by the CHECK INDEX utility.         *
        *                        - Page regression reported by the     *
        *                          DSN1LOGP utility.                   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        For both DB2 V9 and DB2 V10, the process of purging pages from
        the group buffer pool after an object has become non-GBP-
        dependent does not correctly detect the "changed page found"
        condition which may arise when the GBP is allocated in a
        CFLEVEL 17 coupling facility.  If this happens, DB2 leaves
        changed pages in the GBP, which may be encountered again when
        the object once more becomes GBP-dependent.  This can result in
        page regression problems if those pages are no longer current,
        or in castout I/O errors if those pages no longer exist on DASD.

        For DB2 V9, there are a couple of conditions in which a page is
        not properly registered when a buffer pool scan is performed in
        response to a change in the object's P-lock state.  This can
        result in a down-level page being assumed to be current.
        The code which deletes pages from the GBP has been modified to
        correctly detect the "change page encountered" situation (by
        checking only the significant bytes of the reason code).

        The buffer pool scan logic for P-lock transitions has been
        modified to correctly handle registering pages with a read I/O
        in progress.

        The pageset P-lock exit has been modified to ensure that if a
        failure occurs in a buffer pool scan, a re-drive of the exit
        will no longer skip the registration process.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88758
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DOCUMENTATION:
        PM70981 introduces the following changes to externals:

        Changed messages or codes:
1       description of change
        DSNB411I: Page read statistics

        When you specify the DETAIL option, the output includes the page
        read statistics for the buffer pool.

        DSNB411I - RANDOM GETPAGE    =  rgp
                   SYNC READ I/O (R) =  srr
                   SEQ.   GETPAGE    =  sgp
                   SYNC READ I/O (S) =  srs
                   DMTH HIT          =  dmt
                   PAGE-INS REQ      =  pir
                   SEQUENTIAL        =  seq
                   VPSEQT HIT        =  vsh
                   RECLASSIFY        =  rcy

        RANDOM GETPAGE = rgp
            The number of nonsequential GETPAGE requests.
        SYNC READ I/O (R) = srr
            The number of synchronous read I/O operations for
            nonsequential GETPAGE requests.
        SEQ. GETPAGE = sgp
            The number of sequential GETPAGE requests.
        SYNC READ I/O (S) = srs
            The number of synchronous read I/O operations for sequential
            GETPAGE requests.
        DMTH HIT = dmt
            The number of times that the data management threshold was
            reached.
        PAGE-INS REQ = pir
            The number of page-in operations that are required for read
            I/O.
        SEQUENTIAL = seq
            The number of buffers on the sequential least-recently-used
            (SLRU) chain.
        VPSEQT HIT = vsh
            The number of times that the size of the SLRU chain reached
            the sequential steal threshold (the VPSEQT value) for the
            buffer pool.
        RECLASSIFY = rcy
            A statistic that is used by IBM® for serviceability.

        Information about this changed message 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:
        In order for DB2 to use "suppress cross-invalidation"
        enhancement for DELETE_NAME, all of the following must be true:

        - This PTF must be applied to the DB2 member that performs
          castout
        - The GBP must be allocated in a coupling facility of CFLEVEL=17
          or higher. The following CFCC release supports the
          "suppress cross-invalidation" functionality:
          - z114 (2818)
1           DR93G CFCC EC N48162 CFCC Release 17 at the requisite
            microcode load (MCL) level
          - z196 (2817)
            DR93G CFCC EC N48162 CFCC Release 17 at the requisite
            microcode load (MCL) level
          - zEC12 (2827)
            CFCC Release 18
        - The DB2 member that performs castout must be running on z114
          or z196 that supports the "suppress cross-invalidation"
          functionality or a zEC12. The following z/OS releases support
          the "suppress cross-invalidation" functionality:
          - z/OS V1R12 and above with APAR OA38419 installed
      AO:
        PM70981 introduces the following changes to externals:

        Changed messages or codes:
        description of change
        DSNB411I: Page read statistics

        When you specify the DETAIL option, the output includes the page
        read statistics for the buffer pool.

        DSNB411I - RANDOM GETPAGE    =  rgp
                   SYNC READ I/O (R) =  srr
                   SEQ.   GETPAGE    =  sgp
                   SYNC READ I/O (S) =  srs
                   DMTH HIT          =  dmt
                   PAGE-INS REQ      =  pir
                   SEQUENTIAL        =  seq
                   VPSEQT HIT        =  vsh
                   RECLASSIFY        =  rcy

        RANDOM GETPAGE = rgp
            The number of nonsequential GETPAGE requests.
        SYNC READ I/O (R) = srr
            The number of synchronous read I/O operations for
            nonsequential GETPAGE requests.
        SEQ. GETPAGE = sgp
            The number of sequential GETPAGE requests.
        SYNC READ I/O (S) = srs
            The number of synchronous read I/O operations for sequential
            GETPAGE requests.
        DMTH HIT = dmt
            The number of times that the data management threshold was
            reached.
        PAGE-INS REQ = pir
            The number of page-in operations that are required for read
            I/O.
        SEQUENTIAL = seq
            The number of buffers on the sequential least-recently-used
            (SLRU) chain.
        VPSEQT HIT = vsh
            The number of times that the size of the SLRU chain reached
            the sequential steal threshold (the VPSEQT value) for the
            buffer pool.
        RECLASSIFY = rcy
1           A statistic that is used by IBM® for serviceability.

        Information about this changed message will be included in the
        Information Management Software for z/OS Solutions Information
        Center (http://publib.boulder.ibm.com/infocenter/imzic) at a
        later date.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNB5DEL  PM88758

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88758   DSNB5DEL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNB1ABP
       DSNB1AEX
       DSNB1AGB
       DSNB1BVP
       DSNB1CBP
       DSNB1CMD
       DSNB1CNE
       DSNB1CPX
       DSNB1DBP
       DSNB1DVP
       DSNB1GBR
       DSNB1GC1
       DSNB1GD1
       DSNB1GET
       DSNB1GWB
       DSNB1IOR
       DSNB1LRR
       DSNB1PCD
       DSNB1PMI
       DSNB1REL
       DSNB1RWI
       DSNB1TSD
       DSNB5CMX
       DSNB5COM
       DSNB5DEL
       DSNB5PCO
       DSNB5RAP
       DSNB5RDP
       DSNB5STS
       DSNB5ULK
       DSNFBDIR

      MACROS
       DSNDQBST

      LISTEND
 UK95295 COVER LETTER END


 UK95318 COVER LETTER START
1   PROBLEM DESCRIPTION(S):
      PM86069 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 and 10 for z/OS user of using      *
        *                 field procedure (fieldproc) within set       *
        *                 operation (SETOP).                           *
        ****************************************************************
        * PROBLEM DESCRIPTION: An ABEND04E RC00E2000F at location      *
        *                      DSNXEFB.DSNSVSFB: 0858 may occur when   *
        *                      a SQL statement satisfies all of the    *
        *                      following conditions:                   *
        *                      1. a table expression is defined with   *
        *                         set operation(such as: UNION ALL);   *
        *                      2. a column defined with fieldproc and  *
        *                         a constant are referenced in         *
        *                         different SELECT list of full-select *
        *                         under set operation from step #1;    *
        *                      3. an aggregate function with parameter *
        *                         which is from the table expression   *
        *                         defined in step #1 and corresponds   *
        *                         to the column defined with fieldproc *
        *                      4. a GROUP BY clause is used.           *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An ABEND04E RC00E2000F at location DSNXEFB.DSNSVSFB: 0858 may
        occur when a SQL statement satisfies all of the following
        conditions:
        1. a table expression is defined with set operation (such as:
           UNION ALL);
        2. a column defined with fieldproc and a constant are
           referenced in different SELECT list of full-select under the
           set operation from step #1;
        3. an aggregate function with parameter which is from the
           table expression defined in step #1 and corresponds to the
           column defined with fieldproc;
        4. a GROUP BY clause is used.

        The following example helps to illustrate this problem:
        DDL:
        CREATE TABLE TEST.TB
        (C1 CHAR(4) FIELDPROC FPCVD4,
         C2 VARCHAR(4));

        INSERT INTO TEST.TB VALUES('ABCD', 'EFGH');

        SQL:
        SELECT MAX(COL1), COL2
        FROM (SELECT C1, C2
              FROM TEST.TB
                UNION ALL
              SELECT 'EFGH', C2
              FROM TEST.TB) AS TE1 (COL1, COL2)
        WHERE COL1 LIKE 'ABCD%'
        GROUP BY COL2;

1       DB2 missed to issue SQLCODE -415 to block above usage which
        caused ABEND.
        DB2 has been modified correctly to issue SQLCODE -415 to block
        aforementioned usage for avoiding ABEND.

        Additional keywords: SQLFIELDPROC, SQLUNIONALL, SQLGROUPBY

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM86069
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM86069:

        See PM86069 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM86069 corrects a problem of An ABEND04E RC00E2000F at location
        DSNXEFB.DSNSVSFB: 0858 may occur when a SQL statement satisfies
        all of the following conditions:
        1. a table expression is defined with set operation (such as:
           UNION ALL);
        2. a column defined with fieldproc and a constant are
           referenced in different SELECT list of full-select under the
           set operation from step #1
        3. an aggregate function with parameter which is from the
           table expression defined in step #1 and corresponds to the
           column defined with fieldproc;
        4. a GROUP BY clause is used.

        To make this fix effective for a static application, it must 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 PM84536:

        See PM84536 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM84536 corrects a problem of ABEND04E RC00E72018 at location
        DSNXGRDS.DSNXSINE: 1342 when an SQL statement satisfies all of
        the following conditions:
        1. a table expression or VIEW (VW#1) is defined with multiple
           SETOPs;
        2. another table expression or VIEW referenced in VW#1 is also
           defined with multiple SETOPs.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOCAS  PM86069
1      DSNXODSO  PM86069
       DSNXOVD   PM86069

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM86069   DSNXOCAS DSNXODSO DSNXOVD

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOCAS
       DSNXODSO
       DSNXOVD

      LISTEND
 UK95318 COVER LETTER END


 UK95334 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM87905 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of BIND PLAN       *
        *                 with invalid CURRENTSERVER specified.        *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C4 RC00000038 at location         *
        *                      DSNTBMSG offset 543A when BIND          *
        *                      PLAN is issued with an invalid server   *
        *                      name specified for CURRENTSERVER.       *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When DB2 issues warning message DSNT249I for an invalid
        server name, DSNTBMSG does not branch correctly and
        causes the abend.
        DB2 has been fixed to handle the DSNT249I message for an
        invalid server name correctly, and the ABEND0C4 abend no
        longer occurs after the fix.

        Additional keywords: MSGDSNT249I OFFSET543A SQLSPECIALREG
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM87905
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNTBMSG  PM87905

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM87905   DSNTBMSG

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNTBMSG

1     LISTEND
 UK95334 COVER LETTER END


 UK95336 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89197 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of the LOAD        *
        *                 utility involving tables with unique indexes *
        *                 and referential integrity, with parallel     *
        *                 index build.                                 *
        ****************************************************************
        * PROBLEM DESCRIPTION: AE FIX COMPLETION FOR PM84395           *
        *                                                              *
        *                      ABENDS0C4 DSNUGSDA OFFSET539C during    *
        *                      the ENFORCE phase of a LOAD INCURSOR    *
        *                      on a table with unique indexes and      *
        *                      referential integrity.                  *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        AE FIX COMPLETION FOR PM84395

        A LOAD INCURSOR utility with parallel index build was run on a
        table space with unique indexes and referential integrity (RI).
        The utility abended in the ENFORCE phase with an ABEND0C4 in
        DSNUGSDA +x'539C'.  The abend occurred when LOAD attempted to
        position on the SORTOUT data set to read in the foreign keys
        with data set positioning information that was all zeroes.

        During the SORTBLD phase, the SYSUT1 data set is opened.  This
        open acquires a new data set checkpoint control block, copies
        the old block into the new, updates each entry within the block
        with the new address and frees the old checkpoint block.  There
        is a timing window (particularly with small amounts of data)
        where a checkpoint can occur for the SORTOUT data set just prior
        to the creation of the new checkpoint block during the SYSUT1
        open, causing SORTOUT positioning data to be lost.

        Also, if the freed checkpoint storage is immediately reused,
        the LOAD can abend in the SORT phase with ABEND0C4 in
        ICETRYB +x'1D76' with ABEND04E RC00E40347 and other possible
        SORT related abends.

        Additional Keywords: OFFSET1D76 cross-loader crossloader
        LOAD code has been modified to open the SYSUT1 data set prior
        to the attachment of the subtasks in the SORTBLD phase.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89197
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUGSDA  PM89197
1      DSNURPIB  PM89197
       DSNURPPL  PM89197
       DSNURPTB  PM89197

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89197   DSNUGSDA DSNURPIB DSNURPPL DSNURPTB

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUGSDA
       DSNURPIB
       DSNURPPL
       DSNURPTB

      LISTEND
 UK95336 COVER LETTER END


 UK95350 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88804 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 users.                            *
        ****************************************************************
        * PROBLEM DESCRIPTION: Frequent thread terminations without    *
        *                      re-use may result in significant CPU    *
        *                      consumption as 64bit thread pool        *
        *                      storage is freed and REAL frames are    *
        *                      unbacked.                               *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When threads terminate, their pool storage may either be
        completely freed if the thread is not cached for reuse, or a
        portion may be freed.  In either case, storage which is only
        virtually freed by DB2 since it is submanaged, will have its
        REAL frames unbacked in many cases.  This unbacking requires RSM
        latch serialization and also results in a pagefault when those
        pages are again used.  This whole process can show significant
        CPU usage depending on the number of threads and their
        allocation/deallocation frequency.  Similarly, thread
        contraction which may occur at specific commit frequencies, also
        may result in pool storage being virtually freed with the REAL
        frames unbacked.  REALSTORAGE_MANAGEMENT which has default of
        AUTO, should not result in the discard of REAL frames unless the
        LPAR comes under stress and begins paging or nears the
        REALSTORAGE_MAX value if specified.
        This apar changes the way 64 bit Above-the-bar (ATB) real
        storage frames are managed by DB2 based on the DB2 zparms
        REALSTORAGE_MANAGEMENT,REALSTORAGE_MAX and general RSM LPAR
        storage monitor fields.  DB2 ATB storage management is changed
        to no longer issue an IARV64 DISCARDDATA request to free real
        storage frames unless the DB2 storage monitor has detected that
        DISCARD MODE should be turned ON. When DISCARD MODE is ON the
        member will return to the same behavior it had prior to PM88804
1       and issue an IARV64 DISCARDDATA request when freeing storage.

        Not freeing the real storage frames can improve system
        performance due to a significant reduction in first reference
        page faults, RSM lock contention, and uncaptured CPU time.

        *** NOTE ***
        PM88804 may result in higher REAL FRAME counts being reported by
        DB2 monitor reports and RMF, especially in environments that
        never page to aux.  For those customers who experience frequent
        or periodic paging, the counts may not be significantly higher
        but will likely still be higher than before PM88804.  PM88804
        reverses some of the affect of PK25427.
        The major reporting fields for 64 bit storage are:
        qw0225ShrStg_Real - Shared storage most heavily used for threads
                            will likely show the most increase.
        qw0225ComStg_Real - High Common
        qw0225PriStg_Real - High address space private
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88804
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNSCON2  PM88804
       DSNSVSFM  PM88804
       DSNSVSPC  PM88804
       DSNSVSVP  PM88804

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88804   DSNSCON2 DSNSVSFM DSNSVSPC DSNSVSVP

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNSCON2
       DSNSVSFM
       DSNSVSPC
       DSNSVSVP

      LISTEND
 UK95350 COVER LETTER END


 UK95354 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89502 -
        ****************************************************************
        * USERS AFFECTED: For all DB2 for z/OS users who enable star   *
        *                 join and have a query with a table that has  *
        *                 more than 255 columns.                       *
        ****************************************************************
        * PROBLEM DESCRIPTION: Storage overlay can happen when a star  *
        *                      schema query has a snowflake group      *
        *                      dimension and the dimension table       *
1       *                      has more than 255 columns. It may       *
        *                      cause ABEND04E RC00E2000F in DSNXOQSJ   *
        *                      OFFSET+5E1A.                            *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Storage overlay can happen when a star schema query has a
        snowflake group dimension and the dimension table has more
        than 255 columns. The problem may cause ABEND04E RC00E2000F
        in DSNXOQSJ OFFSET+5E1A.

        Additional Keywords:
        SQLSTARJOIN SQLSTORAGE DB2OVRLAY/K OFFSET5E1A
        With logic corrected in DB2 optimizer, the problem is fixed.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89502
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        See PM22534 APAR/PTF text in the PTF cover letter for
        additional information about why a REBIND is necessary.

        PM22534 corrects a storage overlay problem when star join is
        enabled and the number of internal tables created by star join
        processing exceeds the max number of tables supported by DB2.
        After the overlay occurs, various abends can happen.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOQSJ  PM89502

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89502   DSNXOQSJ

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOQSJ

      LISTEND
 UK95354 COVER LETTER END


 UK95360 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM82487 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of Large Objects   *
        *                 (LOBs) with REOPT options.                   *
        ****************************************************************
        * PROBLEM DESCRIPTION: An ABEND04E RC00D31108 can occur at     *
1       *                      location DSNLILLM.DSNLCCLO:0004 when    *
        *                      the following conditions are met for    *
        *                      a given query.                          *
        *                                                              *
        *                      1. When a LOB data type is used as      *
        *                      an input host variable or parameter     *
        *                      marker                                  *
        *                      2. When REOPT(AUTO) is specified.       *
        *                      3. When DB2 is distributed (DRDA).      *
        *                                                              *
        *                      The abend can occur because DB2 may     *
        *                      try to pull the LOB data twice.         *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An ABEND04E RC00D31108 can occur at location
        DSNLILLM DSNLCCLO 0004 when the following conditions are met for
        a given query.

        1.  When a LOB data type is used as an input host variable or
        parameter marker

        2. When REOPT(AUTO) is specified.

        3. When DB2 is distributed (DRDA).

        The abend can occur when DB2 tries to pull the LOB data
        twice. Instead, the data should be pulled only once.

        The following simple query provides an example of a failing
        query.

          UPDATE TBVC01T1
          SET CHARCOL = CAST (? AS CLOB)
          WHERE     INTCOL > ?;

        When the query above is prepared with REOPT options in a DRDA
        environment, DB2 may try to pull the CLOB data twice which
        will result in the abend described above.
        The code in DB2 is modified so that the LOB data is pulled once
        when a REOPT bind option is specified for bind package for
        prepare.

        Please note.
        For the complete solution, apar PM87736 (ptf UK94930) will also
        be needed.

        Additional Keywords: DB2LOB SQLLOB SQLDRDA SQLUPDATE SQLHOSTVAR
                             SQLPMK SQLPMARKER

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM82487
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
1       See PM82487 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM82487 corrects an ABEND04E RC00D31108 problem which can occur
        at location DSNLILLM.DSNLCCLO:0004 when the following conditions
        are met for a given query.

          1. When a LOB data type is used as an input host variable or
             parameter marker.
          2. When REOPT(AUTO) is specified.
          3. When DB2 is distributed (DRDA).

        The abend can occur because DB2 may try to pull the LOB data
        twice.

        To make this fix effective for a static application, it must 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 PM69619 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM69619 corrects a problem that incorrect output may happen
        for a static SQL statement that satisfies all of the
        following conditions:
        1 It references a table which is in PBR(partitioned by range)
          tablespace;
        2 It contains a predicate on VARCHAR column which is a
          partition key of PBR table;
        3 The option REOPT(ALWAYS) or REOPT(VARS) is specified
          when binding the package.

        To make this fix effective for a static application, it must 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 PM35294:

        See PM35294 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM35294 corrects a problem where incorrect output may occur if a
        query contains a host variable or a parameter marker, and a
        special register: CURRENT TIMESTAMP, CURRENT TIME or CURRENT
        DATE, with BIND option REOPT(AUTO).

        To make this fix effective for a static application, it must 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 PM34595:

        A rebind is necessary to rebuild package and/or plan structures
1       based on the changes in this APAR.

        PM34595 corrects a problem that an ABEND0C4 RC00000038 in
        DSNXORRA OFFSET 0DF2 may occur when binding a package or plan
        with bind option REOPT(AUTO) and the package or plan contains
        a query with special register CURRENT DATE, CURRENT TIME or
        CURRENT TIMESTAMP.

        To make this fix effective for a static application, it must 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
       DSNXORHV  PM82487
       DSNXORRA  PM82487

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM82487   DSNXORHV DSNXORRA

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXORHV
       DSNXORRA

      LISTEND
 UK95360 COVER LETTER END


 UK95365 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM87360 -
        ****************************************************************
        * USERS AFFECTED: DB2 9 and 10 for z/OS users of CREATE INDEX  *
        *                 and DROP INDEX.                              *
        ****************************************************************
        * PROBLEM DESCRIPTION: User receives ABEND04E RC00C90110 in    *
        *                      DSNICTBU erqual5004 on a DROP INDEX     *
        *                      statement.                              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The following abends were received during DROP INDEX processing
        when a static insert is concurrently executing against the
        table on which the index is defined:
        ABEND04E RC00C90110 DSNIDM DSNICTBU erqual5004
        ABEND04E RC00C90101 DSNK2DM DSNKINSL erqual5003
        The abends occur due to DB2 incorrectly serializing DROP INDEX
        and CREATE INDEX execution with concurrent DML.  While this
        APAR addresses specific reported symptoms, other symptoms are
        possible.
        DB2 has been changed to obtain a lock of commit duration on
        packages dependent on the base table during execution of CREATE
        INDEX and DROP INDEX, serializing execution of CREATE INDEX
        and DROP INDEX with concurrent DML on the table.  With PM87360
1       applied, concurrently running DML referencing a table on which
        CREATE INDEX or DROP INDEX is executing may result in
        SQLCODE -911 or SQLCODE -904.

        ADDITIONAL KEYWORDS:
        SQLCODE911
        SQLCODE904
        SQLCREATE
        SQLDROP
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM87360
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXIDPM  PM87360

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM87360   DSNXIDPM

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXIDPM

      LISTEND
 UK95365 COVER LETTER END


 UK95368 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89940 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of CORRELATED      *
        *                 subqueries with BETWEEN predicates in EXISTS *
        *                 or IN predicates.                            *
        ****************************************************************
        * PROBLEM DESCRIPTION: An incorrect result set (more rows than *
        *                      expected) can be returned for a query   *
        *                      with a CORRELATED subquery that         *
        *                      contains a BETWEEN predicate in an      *
        *                      EXISTS or IN predicate, and uses a host *
        *                      variable in the BETWEEN predicate which *
        *                      is null.                                *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An incorrect result set (more rows than expected) can be
        returned for a query with a CORRELATED subquery if it contains a
        BETWEEN predicate that uses a host variable which is null in an
        EXISTS or IN predicate.

        The following example helps illustrate a failing scenario.

        1. Create and populate a table.
1
          CREATE TABLE T1(TSCOL TIMESTAMP NOT NULL);
          INSERT INTO T1 VALUES('1994-04-14-15.40.43.296389');
          INSERT INTO T1 VALUES('1993-03-14-15.40.43.296389');


        2. Declare a cursor with a CORRELATED subquery containing a
           BETWEEN predicate in an IN predicate. One of the values in
           the BETWEEN predicate is a host variable with a null value.

          HVINT3 =  0;
          IND3   = -1;

          EXEC SQL DECLARE C1 CURSOR FOR
          SELECT 1 FROM T1 A
          WHERE DATE(TSCOL) IN
          (SELECT DATE(TSCOL) FROM T1 B
           WHERE MONTH(B.TSCOL) BETWEEN :HVINT3:IND3 AND 5
           AND B.TSCOL=A.TSCOL);


        3. Open the cursor and fetch from it.

          EXEC SQL OPEN C1;
          EXEC SQL FETCH C1 INTO :HVINT1:IND1;


        4. Check the results from the execution.

        The above fetch is successfully executed and the host variable
        HVINT1 is assigned the value 1.

           HVINT1 = 1
           IND1   = 0

        However, the query should not qualify any row and an SQLCODE
         +100 is expected.

        DB2 is incorrectly resetting the null indicator for the next
        outer table row.
        Code in DB2 has been modified to avoid resetting the null
        indicator when evaluating the next outer table row for
        a correlated EXISTS or IN subquery.

        Additional Keywords: DB2INCORR/K INCORROUT SQLINCORR
                             SQLINCORROUT SQLCORRSUBQ SQLBETWEEN
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89940
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXRCLS  PM89940
       DSNXREXI  PM89940
       DSNXRSC2  PM89940
1      DSNXRSOR  PM89940

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89940   DSNXRCLS DSNXREXI DSNXRSC2 DSNXRSOR

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXRCLS
       DSNXREXI
       DSNXRSC2
       DSNXRSOR

      LISTEND
 UK95368 COVER LETTER END


 UK95371 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90305 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS utility users of         *
        *                 RUNSTATS INDEX UPDATE NONE REPORT NO.        *
        ****************************************************************
        * PROBLEM DESCRIPTION: Optimization needed for RUNSTATS        *
        *                      TABLESPACE INDEX ALL UPDATE NONE        *
        *                      REPORT NO.                              *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        A RUNSTATS TABLESPACE INDEX ALL UPDATE NONE REPORT NO utility
        was run for the main purpose of invalidating the dynamic
        statement cache.  The utility ran longer than expected.
        Analysis showed that RUNSTATS was scanning the index which
        is not needed for UPDATE NONE REPORT NO processing.
        Code has been modified to avoid scanning the index during a
        RUNSTATS TABLESPACE INDEX ALL UPDATE NONE REPORT NO utility.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM90305
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUSDRB  PM90305

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90305   DSNUSDRB

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUSDRB

      LISTEND
 UK95371 COVER LETTER END
1

 UK95375 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM85937 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of LISTDEF utility *
        *                 with wildcard characters specified.          *
        ****************************************************************
        * PROBLEM DESCRIPTION: LISTDEF with wildcard characters        *
        *                      specified can include directory         *
        *                      objects, causing MSGDSNU064I,           *
        *                      MSGDSNU605I, or other failures when     *
        *                      utilities ran on the LISTDEF list.      *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available.         *
        ****************************************************************
        User used LISTDEF to include all table spaces based on a
        database name which contained a wildcard similar to the
        following:
        LISTDEF LIST INCLUDE TABLESPACES DATABASE D*
        The resulting list included the directory objects in database
        DSNDB01. A RUNSTATS utility against the LIST failed with
        MSGDSNU064I (UTILITY NOT ALLOWED AGAINST SYSTEM DATABASE)
        and MSGDSNU605I (ERROR OCCURRED IN ACCESSING TABLESPACE).

        Other utilities running on a list like this can potentially
        fail in similar ways.
        LISTDEF utility has been modified to ignore all directory
        objects when wildcard characters are specified.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM85937
    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  PM85937

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM85937   DSNUILSA

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUILSA

      LISTEND
 UK95375 COVER LETTER END


 UK95379 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88698 -
        ****************************************************************
        * USERS AFFECTED: All DB2 V9 and 10 for z/OS users of an SQL   *
1       *                 statement that contains special registers in *
        *                 GRPOUP BY and a view or table expression     *
        *                 with UNION ALL.                              *
        ****************************************************************
        * PROBLEM DESCRIPTION: Incorrect output could happen for an    *
        *                      SQL statement that contains special     *
        *                      registers in GRPOUP BY and a view or    *
        *                      table expression with UNION ALL.        *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An example is shown below:

        CREATE TABLE TB1 (A SMALLINT) ;
        CREATE TABLE TB2 (A SMALLINT) ;

        INSERT INTO TB1 VALUES(2006);
        INSERT INTO TB1 VALUES(2007);
        INSERT INTO TB1 VALUES(2007);
        INSERT INTO TB1 VALUES(2008);
        INSERT INTO TB1 VALUES(2008);
        INSERT INTO TB1 VALUES(2008);

        INSERT INTO TB2 VALUES(2008);
        INSERT INTO TB2 VALUES(2008);
        INSERT INTO TB2 VALUES(2008);

        SELECT CASE
                 WHEN A = YEAR(CURRENT DATE) - 7
                   THEN 'VJ6'
                 WHEN A = YEAR(CURRENT DATE) - 6
                   THEN 'VJ7'
                 WHEN A = YEAR(CURRENT DATE) - 5
                  THEN 'VJ8'
                END AS A
              , SUM(1)
        FROM (
            SELECT A FROM TB1
            UNION ALL
            SELECT A FROM TB2
            ) AS TV
        GROUP BY CASE
                   WHEN A = YEAR(CURRENT DATE) - 7
                     THEN 'VJ6'
                   WHEN A = YEAR(CURRENT DATE) - 6
                     THEN 'VJ7'
                   WHEN A = YEAR(CURRENT DATE) - 5
                     THEN 'VJ8'
                 END
        ;

        The query above should return 3 rows when CURRENT DATE is 2013,
        while it only returns 1 row. DB2 did not correctly process the
        aforementioned SQL statements, which caused the incorrect
        output.
        DB2 has been modified to correctly process the aforementioned
1       SQL statement, so there will be no incorrect output.

        Additional keywords: SQLTABLEEXPR SQLVIEW SQLSPECIALREG
                             SQLUNIONALL SQLGROUPBY
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88698
    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.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXODSO  PM88698

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88698   DSNXODSO

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXODSO

      LISTEND
 UK95379 COVER LETTER END


 UK95412 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90480 -
        ****************************************************************
        * USERS AFFECTED: DB2 for z/OS users whose queries utilize     *
        *                 two RANGE predicates against the same        *
        *                 column.                                      *
        ****************************************************************
        * PROBLEM DESCRIPTION: The compound filter factor can be       *
        *                      inaccurately estimated for two RANGE    *
        *                      predicates against the same TIMESTAMP   *
        *                      column, and this may cause DB2 to       *
        *                      choose an inefficient access path.      *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An inefficient access path may be chosen because the compound
1       filter factor of two RANGE predicates against the same TIMESTAMP
        column can be inaccurately estimated.  It is also possible,
        although less likely, to have this problem for other datatypes.

        Additional Keywords:
        SQLTIMESTAMP FILTERFACTOR SQLACCESSPATH SQLPERFORMANCE
        Code is changed to correct the filter factor calculation
        for the situation described above.  DB2 will have a better
        chance to choose more efficient access paths for these
        types of queries.  As with any change to DB2 query
        optimization that can drive a different access path,
        there is some risk of query performance regression.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM90480
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM90480:

        See PM90480 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM90480 corrects a problem of inaccurate compound filter
        factor of two RANGE predicates on the same column which
        may result in an inefficient access path.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOCCF  PM90480

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90480   DSNXOCCF

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOCCF

      LISTEND
 UK95412 COVER LETTER END


 UK95443 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89560 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 for zOS.                    *
        ****************************************************************
        * PROBLEM DESCRIPTION: 1 - ABEND0C4 in DSNJDS05 following an   *
        *                      IO error reading an archive log data    *
        *                      set.                                    *
1       *                      2 - ABEND0C4 in DSNJR103 running a      *
        *                      RECOVER utility following a             *
        *                      conditional restart of DB2 that         *
        *                      truncated the logs at the end of an     *
        *                      archive log data set.                   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        1 - An ABEND0C4 occurred in DSNJDS05 following an IO error
        reading an archive log on dasd.  Residual tracking information
        resulted in an unnecessary CHECK during CLOSE processing
        following the log read IO error (MSGDSNJ132I).  The ABEND0C4
        occurred on the expansion of the CHECK macro in DSNJDS05.
        2 - During a remote site recovery test, an archive log data
        set was added to the BSDS with an ENDRBA value that was less
        than the actual ENDRBA value, which logically truncated the
        archive log data set.  A conditional restart was then done
        with the supplied archive ENDRBA value + 1.  Since DB2 did
        not truncate the archive log during the conditional restart,
        DB2 did not set the TRUNCATED flag in the BSDS.  This caused
        archive read to process the entire last block of the archive
        data set instead of stopping at the ENDRBA of the archive
        log registered in the BSDS.  This resulted in an ABEND0C4
        in DSNJR103 attempting to assemble the segments of a
        spanned log record.
        1 - Residual tracking information will be reset in the archive
        read SYNAD exit to prevent an invalid CHECK during CLOSE
        processing following an IO error reading an archive log data
        set on dasd.
        2 - Archive read will only process log records up to the
        ENDRBA value registered in the BSDS when the archive log
        has been logically truncated by DSNJU003.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89560
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNJDS05  PM89560
       DSNJR106  PM89560

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89560   DSNJDS05 DSNJR106

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNJDS05
       DSNJR106

      LISTEND
 UK95443 COVER LETTER END


 UK95466 COVER LETTER START
1   PROBLEM DESCRIPTION(S):
      PM89138 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of REPORT RECOVERY *
        *                 utility.                                     *
        ****************************************************************
        * PROBLEM DESCRIPTION: Customer ran a REPORT RECOVERY INDEX    *
        *                      ALL on an actively updated table space  *
        *                      with 4096 partitions.  In the absence   *
        *                      of the CURRENT keyword, the report to   *
        *                      be printed was extremely large.         *
        *                      Storage below the bar in the DBM1       *
        *                      address space was exhausted causing     *
        *                      abend ABEND04E RC00E20016 in module     *
        *                      DSNSVSTK OFFSET0636 and DB2 came down.  *
        ****************************************************************
        * RECOMMENDATION: Apply the corrective PTF.                    *
        ****************************************************************
        Storage for REPORT RECOVERY was being obtained below the bar.
        The extreme size of the report lead to exhausting storage
        and the subsequent termination of DB2.

        The occurrence of this problem is very rare and is affected
        by several factors which combine to produce extremely large
        reports:
           *  REPORT RECOVERY on objects which were created long ago
           *  Infrequent execution of the MODIFY RECOVERY utility
           *  A table space with a large number of partitions
           *  Heavily updated table spaces and indexes
           *  The absence of the CURRENT keyword on REPORT RECOVERY
           *  A large number of COPY YES indexes with the INDEX ALL
              keywords specified on REPORT RECOVERY
        REPORT RECOVERY storage is now obtained above the bar.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89138
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUPBSD  PM89138
       DSNUPCPY  PM89138
       DSNUPLGR  PM89138
       DSNUPPBS  PM89138
       DSNUPPCP  PM89138
       DSNWDFUT  PM89138

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89138   DSNUPBSD DSNUPCPY DSNUPLGR DSNUPPBS DSNUPPCP DSNWDFUT

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUPBSD
       DSNUPCPY
       DSNUPLGR
1      DSNUPPBS
       DSNUPPCP
       DSNWDFUT

      LISTEND
 UK95466 COVER LETTER END


 UK95475 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90594 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users that use IFCID     *
        *                 306 to retrieve log records from multiple    *
        *                 members of a DB2 data sharing group.         *
        ****************************************************************
        * PROBLEM DESCRIPTION: IFCID 306 requests may return end of    *
        *                      scope (EOS) for a given ending LRSN     *
        *                      value when log records are returned     *
        *                      from one or more members with the       *
        *                      specified ending LRSN.  A subsequent    *
        *                      IFCID 306 request may receive a log     *
        *                      record with a LRSN lower than the       *
        *                      previous EOS value from one or more     *
        *                      members that did not return a log       *
        *                      record matching the EOS value of the    *
        *                      previous request.  The log records      *
        *                      for a given member are returned in      *
        *                      order.  The merged set of log records   *
        *                      as returned by IFCID 306 may be out     *
        *                      of order between members.               *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The initial IFCID 306 call writes the log buffers from all
        members of a data sharing group to DASD.  This is done first
        on the host member and then on other members via a IRLM notify.
        If a log record spans multiple log control intervals, in some
        situations the process of externalizing the log buffers may not
        write the full log record to DASD.  If an ensuing IFCID 306 read
        request reads the partially written log record before some other
        process has externalized the remainder of the log record, the
        record is not returned via IFCID 306 because it is not yet
        complete on DASD.  The record will be returned if another IFCID
        306 read request is issued.  This may cause the record to be
        returned out of LRSN sequence when compared to log records
        already returned from other members on the previous IFCID 306
        request.
        The process of externalizing log records for all members of a
        data sharing group has been changed to ensure that the entire
        spanned record will be written to DASD prior to being read by
        an IFCID 306 request.

        For this change to be fully effective, it must be applied to
        all members of a data sharing group.  The PTF may be applied
        one member at a time in any order.  There is no need to apply
1       the PTF first to the member that is servicing the IFCID 306
        requests.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM90594
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNJNTFY  PM90594
       DSNJW004  PM90594

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90594   DSNJNTFY DSNJW004

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNJNTFY
       DSNJW004

      LISTEND
 UK95475 COVER LETTER END


 UK95476 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86364 -
        ****************************************************************
        * USERS AFFECTED: DB2 data sharing users.                      *
        ****************************************************************
        * PROBLEM DESCRIPTION: A pageset or partition is invalidly     *
        *                      put into LPL, with MSGDSNB250E showing  *
        *                      a page range of X'00000000' to          *
        *                      X'FFFFFFFF', an LPL TRACE ID of 4, and  *
        *                      an LPL REASON TYPE of CASTOUT.          *
        *                                                              *
        *                      The LPL message may be followed by an   *
        *                      ABEND04E RC00C20221 in DSNB5DEL.        *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Castout processing will put an entire pageset or partition into
        LPL if the object it is invoked for is not physically open.
        Castout won't normally be invoked on a member who doesn't have
        the object open, but it can happen if another member failed to
        detect that it was the last updating member.  This detection can
        fail due to a timing window in which the pageset castout P-lock
        cannot be upgraded to state X because a structure castout engine
        is holding it temporarily in state IS.
        The pageset castout last-updater detection has been modified to
        attempt to upgrade the pageset castout P-lock to state SIX
        instead of state X, so that it will be incompatible only with
        other updaters, and not with a structure castout engine who
        only acquires the P-lock for notification purposes.
    COMPONENT:  5740-XYR00-HDBAA10
1   APARS FIXED: PM86364
    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  PM86364

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM86364   DSNB1CPL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNB1CPL

      LISTEND
 UK95476 COVER LETTER END


 UK95478 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88576 -
        ****************************************************************
        * USERS AFFECTED: DB2 data sharing users.                      *
        ****************************************************************
        * PROBLEM DESCRIPTION: Castout processing delayed due to       *
        *                      repeated timeouts on read_coclass       *
        *                      calls.  This may result in application  *
        *                      timeouts, most likely on write drain    *
        *                      locks held by correlation-ID            *
        *                      010.PM2PCP01 or 010.PM2CSX01.           *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        If castout processing for a pageset or partition encounters a
        timeout on a read_coclass request during "build page list"
        processing - probably due to a large number of pages in the
        castout class belonging to other objects - it does not correctly
        drive the next request with a restart token.  Because of this,
        it may continue to repeatedly encounter timeouts, delaying the
        completion of the castout, and possibly causing applications to
        time out on a write drain lock.

        A similar problem exists for the case where the read_coclass
        hits a "full list" condition, but the pages returned cannot 
be
 
        cast out - possibly due to I/O errors.  The "build page list"
        processing may repeatedly come back with the same page list
        rather than moving on and eventually running out of pages.
        The "build page list" logic for castout has been modified to
        correctly use the restart token when redriven after hitting a
        timeout or a "buffer full" condition.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88576
    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
       DSNB5BPL  PM88576

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88576   DSNB5BPL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNB5BPL

      LISTEND
 UK95478 COVER LETTER END


 UK95479 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM87865 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 9 and DB2 10 for z/OS who   *
        *                 use the REOPT(AUTO) bind option              *
        ****************************************************************
        * PROBLEM DESCRIPTION: A query using host variables and the    *
        *                      REOPT(AUTO) bind option may go into     *
        *                      an endless loop                         *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        A query using host variables or parameter markers and the
        REOPT(AUTO) bind option could get into an endless loop.

        A bitmap is set incorrectly, which could be used later on
        to determine an exit condition for a loop.  With the
        incorrect bitmap setting, the exit condition never became
        true, so execution was caught in an endless loop.

        Additional Keywords:
        ENDLESS LOOP LOOPING INFINITE LOOPDSNXOGNC LOOPDSNXOCCF
        SQLHOSTVAR PARAMETERMARKER SQLPMARKER SQLPMK
        SQLREOPTAUTO REOPTAUTO
        Code was changed to set the bitmap correctly.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM87865
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        A rebind is necessary to rebuild package and/or plan structure
        based on the changes in this APAR.

        PM42530 corrects a problem that an ABEND0CF RC0000000F in
        DSNXORRA OFFSET 0B74 may occur when executing a package or plan
        with bind option REOPT(AUTO) and the plan used has a R-scan
        with cost of 7FFFFFFF.
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
       DSNXORAC  PM87865

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM87865   DSNXORAC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXORAC

      LISTEND
 UK95479 COVER LETTER END


 UK95484 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86966 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS V10 parallelism users.      *
        ****************************************************************
        * PROBLEM DESCRIPTION: The query can not run in parallelism    *
        *                      although the explain results show that  *
        *                      a parallelism plan is chosen during     *
        *                      the bind time.                          *
        *                                                              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The query can not run in parallelism although the explain
        results show that a parallelism plan is chosen during the bind
        time.

        DB2 did not calculate the minimal I/O streams need from the
        buffer pool correctly and caused this parallelism degeneration.
        SOLUTION:
        DB2 has been fixed to correctly calculate the minimal I/O
        streams need from the buffer pool.

        Additional Keywords: SQLPARALLELISM DB2PARALL/K
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM86966
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXRBMN  PM86966

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1      PM86966   DSNXRBMN

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXRBMN

      LISTEND
 UK95484 COVER LETTER END


 UK95494 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88257 -
        ****************************************************************
        * USERS AFFECTED: All DB2 users using indexes.                 *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C20101 in DSNB1GFP         *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        DB2 keeps a token list for index root page buffers that are
        pinned in the buffer pool for a fast GetPage. The token list
        becomes invalid when ALTER INDEX BUFFERPOOL switches to a
        different buffer pool. When an invalid token is used, DB2
        encounters an unexpected error as it no longer finds the
        buffer in the new buffer pool and causes an abend.
        DB2 has been fixed to reset the token list pointer to zero if
        an invalid token condition is detected. The zero token list
        pointer will be set to a valid pointer again during a
        subsequent fast Getpage as the root page buffers get pinned in
        the buffer pool.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88257
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNB1GFP  PM88257

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88257   DSNB1GFP

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNB1GFP

      LISTEND
 UK95494 COVER LETTER END


 UK95495 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90218 -
1       ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS V9 and V10 users who need   *
        *                 an updated copy of the Diagnosis Guide       *
        *                 and Reference.                               *
        ****************************************************************
        * PROBLEM DESCRIPTION: This APAR provides updated PDF files    *
        *                      of the DB2 for z/OS V9 and V10          *
        *                      Diagnosis Guide and Reference.          *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        This APAR provides the following versions of the DB2
        Diagnosis Guide and Reference in PDF format:
        V9:  LY37-3218-09
        V10: LY37-3220-06
        These are the same versions of these documents that are
        available on the latest DB2 for z/OS licensed library
        collection.
        This APAR provides the following versions of the DB2
        for z/OS Diagnosis Guide and Reference in PDF format:
        V9:  LY37-3218-09
        V10: LY37-3220-06
        To read these documents, download them as binary to your PC
        or other system that has a PDF reader, such as the Adobe
        Acrobat Reader.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM90218
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNDR     PM90218

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90218   DSNDR

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MACROS
       DSNDR

      LISTEND
 UK95495 COVER LETTER END


 UK95497 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86596 -
        ****************************************************************
        * USERS AFFECTED: All DB2 users of workfile database.          *
        ****************************************************************
        * PROBLEM DESCRIPTION: When growing new partition for PBG      *
        *                      table space in workfile database, after *
        *                      repeatedly receiving the DEFINE/CREATE  *
        *                      faliure,                                *
1       *                                                              *
        *                      DSNP002I DEFINE FAILED RC=00D70025      *
        *                      DSNP016I CREATE FAILED RC=00D70025      *
        *                                                              *
        *                      users may receive the following DBD     *
        *                      pool full message,                      *
        *                      DSNT500I DSNGEDLC RESOURCE UNAVAILABLE  *
        *                      REASON 00C90089                         *
        *                      TYPE 00000602                           *
        *                      NAME EDM DBD SPACE                      *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When PGB grows a new partition, DB2 needs to create a new OBD.
        If DB2 hit an error during creating the partition, the storage
        for the new OBD is not released. When the failure of growing
        partition occurs repeatly, DBD pool could be full.
        DB2 has been changed to free the storage allocated for workfile
        PBG table space OBD if an error happens.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM86596
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNGDCOS  PM86596
       DSNGDLOG  PM86596

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM86596   DSNGDCOS DSNGDLOG

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNGDCOS
       DSNGDLOG

      LISTEND
 UK95497 COVER LETTER END


 UK95511 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM75595 -
        ****************************************************************
        * USERS AFFECTED: DB2 10 for z/OS users of DROP TABLESPACE     *
        *                 when IFCID 58 trace is turned on.            *
        ****************************************************************
        * PROBLEM DESCRIPTION: The type of SQL request is not being    *
        *                      set in IFCID 58 for DROP TABLESPACE     *
        *                      statements.                             *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        On a DROP TABLESPACE statement, the type of SQL request as
1       displayed in IFCID 58 field QW0058TOS is incorrect (containing
        '00'X).
        DB2 has been changed to correctly set QW0058TOS (to 'E7'X)
        for DROP TABLESPACE IFCID 58 trace records.

        ADDITIONAL KEYWORDS:
        SQLDROP
        IFCID058
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM75595
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXI14   PM75595

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM75595   DSNXI14

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXI14

      LISTEND
 UK95511 COVER LETTER END


 UK95538 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88165 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 users.                            *
        ****************************************************************
        * PROBLEM DESCRIPTION: Opening more than 100000 datasets,      *
        *                      requires more DB2 Buffer Manager        *
        *                      control blocks than will currently fit  *
        *                      into the maximum storage pool size.     *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The amount of storage currently allowed in any 64bit pool is
        capped at 2GB.  This will not support the number of control
        blocks required for 200000 concurrent open datasets.
        Code has been changed to allow pool definitions up to 4GB.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88165
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNB1PMI  PM88165
       DSNSVSVP  PM88165

1     CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88165   DSNB1PMI DSNSVSVP

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNB1PMI
       DSNSVSVP

      LISTEND
 UK95538 COVER LETTER END


 UK95544 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89078 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of INLIST          *
        *                 table access when using FIELDPROCS.          *
        ****************************************************************
        * PROBLEM DESCRIPTION: An incorrect result set can be returned *
        *                      for a query that contains an INLIST     *
        *                      table access with a field procedure     *
        *                      defined on the INLIST column.           *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An incorrect result set can be returned for a query that
        contains an INLIST table access with a field procedure defined
        on the INLIST column.  In the reported case, the result set was
        empty.


        The following example can help to illustrate a failing case.

          CREATE TABLE T1 (C1 CHAR(36) FIELDPROC TEST1,C2 CHAR(2));


          CREATE  INDEX IX1 ON T1(C1) ;
          CREATE INDEX IX2 ON T1(C2);

         INSERT INTO T1 VALUES
          ('42869ac4-4069-11dc-aa15-530f6a1c033a','AK');
         INSERT INTO T1 VALUES
          ('a82fd1c6-1ddd-11de-849d-530f671c0194','AS');

        Define the following two host variable values

        Hv1: = '42869ac4-4069-11dc-aa15-530f6a1c033a'
        Hv2: = 'a82fd1c6-1ddd-11de-849d-530f671c0194'


        Perform the following query.

         SELECT C1
            FROM T1
1        WHERE C1 IN (:Hv1, :Hv2) AND C2 IN  ('AK','AS');

        No rows are returned. The correct result is two rows.

                   +--------------------------------------+
                   |                  C1                  |
                   +--------------------------------------+
                 1_| 42869ac4-4069-11dc-aa15-530f6a1c033a |
                 2_| a82fd1c6-1ddd-11de-849d-530f671c0194 |
                   +--------------------------------------+
        DB2 code has been fixed to return correct result
        when we have inlist table access with field proc

        Additional keywords : SQLIN SQLFIELDPROC SQLINLISTTABLE
                              SQLHOSTVAR SQLINCORR INCORROUT
                              DB2INCORR/K  SQLINCORROUT
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89078
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM89078:

        See PM89078 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM89078 corrects incorrect output for an SQL statement with
        inlist table access and field proc

        To make this fix effective for a static application, it must 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
       DSNXGINL  PM89078

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89078   DSNXGINL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXGINL

      LISTEND
 UK95544 COVER LETTER END


 UK95551 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM80900 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS utility users of         *
        *                 DSN1PRNT using keyword FORMAT                *
1       ****************************************************************
        * PROBLEM DESCRIPTION: DSN1PRNT specifying the FORMAT option   *
        *                      processing a space map page may abend   *
        *                      with:                                   *
        *                      + ABEND0C4 RC11                         *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When DSN1PRNT is run with the FORMAT parameter, while
        processing a segmented space map page, it may attempt
        to process data past the end of the page and abend
        with ABENDS0C4 R11.
        DSN1PRNT is modified to prevent the abend on a space map page.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM80900
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSN1DFPG  PM80900

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM80900   DSN1DFPG

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSN1DFPG

      LISTEND
 UK95551 COVER LETTER END


 UK95553 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM72190 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS users.                      *
        ****************************************************************
        * PROBLEM DESCRIPTION: An ABEND0D6 RC00000026 occurs in        *
        *                      DSN3SSTM during DB2 shutdown.           *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An ABEND0D6 RC00000026 may occur in module DSN3SSTM if the
        module tries to issue msgDSN3001I or msgDSN3007I.  This problem
        only occurs in DB2 V10 for z/OS.
        ABEND0D6 RSN00000026
        DB2 has been updated so module DSN3SSTM can correctly issue
        msgDSN3001I and msgDSN3007I.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM72190
    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
       DSN3SSTM  PM72190

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM72190   DSN3SSTM

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSN3SSTM

      LISTEND
 UK95553 COVER LETTER END


 UK95633 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM80707 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of RESTORE SYSTEM  *
        *                 utility with FROMDUMP specified.             *
        ****************************************************************
        * PROBLEM DESCRIPTION: RESTORE SYSTEM FROMDUMP may attempt     *
        *                      to restore a system level backup        *
        *                      which has not been dumped to tape,      *
        *                      or may fall back and attempt to         *
        *                      do so after a prior failure.            *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
          This APAR improves the way RESTORE SYSTEM with FROMDUMP
        chooses the system level backup (SLB) it will attempt to
        restore, or fall back to, in order to address several
        problems.

          1. If FROMDUMP is specified, RESTORE SYSTEM may choose an
        SLB to restore which has not been dumped to tape, causing the
        RESTORE to fail or to fall back to an earlier SLB.

          2. If FROMDUMP is specified and the restore of the most
        recent SLB fails, it may fall back and attempt to restore a
        previous SLB.  If that SLB is only on disk, the RESTORE will
        fail, and will not attempt to fall back further.

          3. If RESTORE SYSTEM fails to restore an SLB, but falls
        back to an earlier SLB and restores it successfully, the
        RESTORE SYSTEM utility ends with RC8 and DB2 will function as
        though the system has not been properly recovered.

          Messages related to these issues include the following:

        MSGDSNU1631I - RESTORE SYSTEM UTILITY FAILED BECAUSE THE
                       CALL TO DFSMSHSM FAILED.  SEE THE HSM
                       ACTIVITY LOG FOR HSM MESSAGES INDICATING THE
                       CAUSE OF THE ERROR.
1
        MSGDSNU1616I - THE CALL TO DFSMSHSM TO RECOVER SYSTEM
                       FAILED.  PLEASE SEE MESSAGE ARC1806E IN THE
                       HSM ACTIVTY LOG.  A RETRY MAY BE ATTEMPTED
                       IF AN APPROPRIATE BACKUP VERSION CAN BE
                       IDENTIFIED.

        MSGDSNU1619I - RESTORE SYSTEM UTILITY FAILED, BECAUSE
                       THERE ARE NO BACKUP SYSTEM HISTORY ENTRIES
                       IN THE BSDS WITH A DATA COMPLETION
                       LRSN/RBA PRIOR TO THE LOG TRUNCATION POINT

        MSGDSNU1637I - RESTORE SYSTEM UTILITY FAILED BECAUSE NO
                       FLASHCOPY IS AVAILABLE

        MSGDSNR050I  - DB2 STARTED IN SYSTEM RECOVER PENDING MODE

        MSGDSNY014I  - DB2 WAS STARTED WITH ACCESS(MAINT)

        additional keywords:  DSNU1631I DSNU1616I DSNU1619I DSNU1637I
                              DSNR050I DSNY014I DSNU1618I
          RESTORE SYSTEM utility code was changed so that when FROMDUMP
        is specified (or requested via ZPARM setting
        RESTORE_RECOVER_FROMDUMP = YES), only system level backups that
        have been dumped to tape will be used to restore.  If the most
        recent SLB on tape prior to the requested log truncation point
        fails, the next most recent SLB on tape will be used.
          A change to the DB2 documentation is made, similar to the
        following:
          DB2 messages
        MSGDSNU1618I - RESTORE SYSTEM UTILITY FAILED BECAUSE THERE ARE
                       NO BACKUP SYSTEM HISTORY ENTRIES IN THE BSDS
        and
        MSGDSNU1619I - RESTORE SYSTEM UTILITY FAILED, BECAUSE THERE ARE
                       NO BACKUP SYSTEM HISTORY ENTRIES IN THE BSDS
                       WITH A DATA COMPLETION LRSN/RBA PRIOR TO THE LOG
                       TRUNCATION POINT

        will both have the following text added to their existing
        respective Explanations:

        If you ran RESTORE SYSTEM with the FROMDUMP option, references
        in this message to BACKUP SYSTEM history entries refer only to
        history entries for backups that were dumped to tape.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM80707
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        The PTF for APAR PM80707 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
1       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
       DSNUVARS  PM80707
       DSNUVBRD  PM80707

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM80707   DSNUVARS DSNUVBRD

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUVARS
       DSNUVBRD

      LISTEND
 UK95633 COVER LETTER END


 UK95655 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89402 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS users.                      *
        ****************************************************************
        * PROBLEM DESCRIPTION: A DB2 RRSAF thread is hung after an     *
        *                      ABEND04E RC00E50013.  DB2 cancel        *
        *                      thread, MVS CANCEL and MVS FORCE        *
        *                      cannot end the DB2 thread.              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        A DB2 RRSAF thread is hung after an ABEND04E RC00E5013.  The
        thread cannot be terminated with a DB2 cancel thread command or
        an MVS CANCEL and FORCE command.
        RSN00E50013
        DB2 RRSAF recovery has been updated to avoid this problem with
        cancelling RRSAF threads.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89402
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSN3RRSF  PM89402

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89402   DSN3RRSF

1     THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSN3RRSF

      LISTEND
 UK95655 COVER LETTER END


 UK95657 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90175 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS utility users of the     *
        *                 RECOVER utility.                             *
        ****************************************************************
        * PROBLEM DESCRIPTION: New function is required to handle      *
        *                      coexistence when moving to the          *
        *                      following release.                      *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Code is being added to support a future function of DB2.
        Code is being added to support a future function of DB2.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM90175
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNFMDIR  PM90175
       DSNFUDRB  PM90175
       DSNFUDRD  PM90175
       DSNUGPPL  PM90175
       DSNUGPRT  PM90175
       DSNUGPRZ  PM90175
       DSNUMSGB  PM90175
       DSNUMSGD  PM90175

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90175   DSNFMDIR DSNFUDRB DSNFUDRD DSNUGPPL DSNUGPRT DSNUGPRZ
                 DSNUMSGB DSNUMSGD

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNFMDIR
       DSNFUDRB
       DSNFUDRD
       DSNUGPPL
       DSNUGPRT
       DSNUGPRZ
       DSNUMSGB
       DSNUMSGD

1     LISTEND
 UK95657 COVER LETTER END


 UK95658 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90247 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS utility users of the     *
        *                 RECOVER utility.                             *
        ****************************************************************
        * PROBLEM DESCRIPTION: This is an activation APAR for the      *
        *                      utility tool feature APAR PM90175.      *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Apply this APAR to activate PM90175.
        Apply this APAR to activate PM90175.
    COMPONENT:  5740-XYR00-JDBAA1K
    APARS FIXED: PM90247
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUFFML  PM90247

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90247   DSNUFFML

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUFFML

      LISTEND
 UK95658 COVER LETTER END


 UK95661 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM85893 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS       *
        *                 users of DSN1CHKR utility.                   *
        ****************************************************************
        * PROBLEM DESCRIPTION: DB2 issues MSGDSN1835I, MSGDSN1807I     *
        *                      and MSGDSN1802I during DSN1CHKR on      *
        *                      the object that is composed of more     *
        *                      than 9 pieces.                          *
        *                      Only the first 9 pieces are checked     *
        *                      and the rest pieces are unchecked.      *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When DSN1CHKR is run against an object that is composed of more
1       than 9 data sets, DB2 converts HEX value to an incorrect char
        value for the name of 10th data set during processing.
        Thus only the first 9 data sets are checked and the rest are
        ignored.
        DB2 code has been modified to convert the HEX value to the
        correct char value when DSN1CHKR processes an object that has
        more than 9 data sets.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM85893
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSN1BUFM  PM85893

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM85893   DSN1BUFM

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSN1BUFM

      LISTEND
 UK95661 COVER LETTER END


 UK95681 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86412 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS utility users of REORG   *
        *                 AUX YES COPYDDN wanting TEMPLATE switching   *
        *                 for the image copies                         *
        ****************************************************************
        * PROBLEM DESCRIPTION: IGD17279I message(s) issued for REORG   *
        *                      TABLESPACE AUX YES requesting TEMPLATE  *
        *                      switching to tape for LOB table         *
        *                      space(s) and the REORG utility abends   *
        *                      with ABEND04E RC00E40346                *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        REORG TABLESPACE AUX YES COPYDDN(template name) was run
        utilizing TEMPLATE switching for the inline copy of both the
        base table space and LOB table space(s).  Prior to this APAR,
        REORG TABLESPACE AUX YES COPYDDN did not support template
        switching for the LOB table space(s).  The inline copies for the
        LOB table space(s) were placed on disk rather than tape as
        desired.  Because the LOB was so large, MSGIGD17279I n VOLUMES
        WERE REJECTED BECAUSE OF A DADSM FAILURE (044E0097) was issued
        and the REORG abended with ABEND04E RC00E40346.

        REORG TABLESPACE AUX YES COPYDDN should support TEMPLATE
        switching for the LOB table space(s).
1       REORG TABLEPSACE AUX YES COPYDDN now supports TEMPLATE switching
        for inline copies of LOB table spaces but only for STACK NO.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM86412
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNURAIC  PM86412

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM86412   DSNURAIC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNURAIC

      LISTEND
 UK95681 COVER LETTER END


 UK95718 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM83972 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users.         *
        ****************************************************************
        * PROBLEM DESCRIPTION: Under the same COMMIT scope, if an      *
        *                      application holds an X lock on some     *
        *                      catalog table due to the execution of   *
        *                      some DDL statement, then runs a package *
        *                      which incurs an autobind, and then      *
        *                      performs a ROLLBACK for some reason,    *
        *                      the autobind actions are not part       *
        *                      of the rollback process. This may cause *
        *                      the following abend to be received:     *
        *                      ABEND04E RC00C90101 DSNICUBC ERQUAL500B *
        *                      ERQUAL5013 due to catalog corruption.   *
        *                                                              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The reason this abends is because autobind is performed by a
        separate service task, but it always shares locks with the
        application. This incorrect locking strategy caused the catalog
        corruption and the abend during recovery.

        Additional Keywords:
        ABEND04E RC00C90101 ERQUAL500B ERQUAL5013 SQLLOCK

        Code has been changed to use the right locking strategy as in
        DB2 V8. If the application has an X lock on some catalog table,
        autobind is performed under the same agent so that it can be
        rolled back with the application.
1   COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM83972
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DOCUMENTATION:
        PM69542 introduces the following changes to externals:

        DB2 10 for z/OS has been changed to disregard the
        REMOTE(location-name,...,<luname>,...) bind option when it
        allocates packages for an application.

        DB2 will continue to validate all remote connections if
        ENABLE(REMOTE) or DISABLE(REMOTE) is specified. If
        REMOTE(location-name,...,< luname>,...) is also specified,
        it is ignored during package allocation.

        Information about this change will be
        included in the Information Management Software for z/OS
        Solutions Information Center
        (http://publib.boulder.ibm.com/infocenter/imzic) at a later
        date.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNTAAL   PM83972
       DSNTBAB   PM83972
       DSNXAAB   PM83972
       DSNXEAAL  PM83972

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM83972   DSNTAAL  DSNTBAB  DSNXAAB  DSNXEAAL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNTAAL
       DSNTBAB
       DSNXAAB
       DSNXEAAL

      LISTEND
 UK95718 COVER LETTER END


 UK95721 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88656 -
        ****************************************************************
        * USERS AFFECTED: All users of Java stored procedures in DB2   *
        *                 9 for z/OS and DB2 10 for z/OS are affected  *
        *                 by this change.                              *
        ****************************************************************
        * PROBLEM DESCRIPTION: Calls to Java stored procedures fail    *
        *                      with SQLCODE -551 (authorization error) *
        *                      and the following message is seen in    *
        *                      the WLM task log:                       *
1       *                        DSNX961I  DSNX9WLJ ATTEMPT TO PERFORM *
        *                        OPERATION FindClass FAILED FOR        *
        *                        ROUTINE schema.name.                  *
        *                        SSN= DSN                              *
        *                        PROC= procname ASID= nnnn             *
        *                          CLASS= path/subpath                 *
        *                          METHOD= methodOffset                *
        *                        ERROR INFO=                           *
        *                          path.subpath                        *
        *                          schema.name java.sql.SQLException:  *
        *                        SQLCODE: -551                         *
        *                        SQLERRMC=DB2XSFA schema               *
        *                          EXECUTE PACKAGE DSNJAR.DSNX9LDJ,    *
        *                          Get release info                    *
        ****************************************************************
        * RECOMMENDATION: Apply the fixing PTF for this APAR.          *
        ****************************************************************
        DB2 module DSNX9LDJ loads jarfiles that contain classes needed
        to execute a Java stored procedure.  DB2 installation binds a
        package for DSNX9LDJ in the DSNJAR collection ID but does not
        grant execute access on the package.  Callers that attempt to
        use DSNX9LDJ will experience the SQLCODE -551 error noted in
        the PROBLEM DESCRIPTION area of this APAR.

        In response, this APAR makes the following changes:

        - In DB2 10 only, the bind statement for package
          DSNJAR.DSNX9LDJ is moved from DSNTIJRT (program DSNTRIN) to
          job DSNTIJSG, job step DSNTIRU.  (In DB2 9, that bind
          statement already exists in DSNTIJSG).

        - In DB2 9 and 10, a statement to grant execute access on
          package DSNJAR.DSNX9LDJ is added to job DSNTIJSG, job
          step DSNTIJG.  The grant is to PUBLIC but can be changed to
          one or more specific authorization IDs that call Java stored
          procedures.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88656
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        ***Action for PM88656 (DB2 10 for z/OS)

        This PTF adds statements to job DSNTIJSG to bind and grant
        access on DSNX9LDJ, the package for the DB2 stored procedures
        Java class loader.

        If you have already installed or migrated to DB2 10 then you
        need to take the following actions after applying this PTF:
        (1) Update private copies of the installation CLIST
        (2) Update your customized copy of job DSNTIJSG
        (3) Grant execute access on package DSNX9LDJ

        Detailed guidance for these actions follows:
        ----------------------------------------------------------------
1       (1) Update private copies of the installation CLIST
            ***********************************************************
            * All customers need to perform this step
            ***********************************************************
            This PTF modifies the DB2 installation CLIST member
            DSNTINS1 in the prefix.SDSNCLST target library.
            After applying this PTF, you need to redo any record format
            changes and reapply any tailoring you have done to your
            copies of DSNTINS1.  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 DSNTIJSG
            ***********************************************************
            * All customers who maintain a private copy of DSNTIJSG
            * need to perform this step
            ***********************************************************
            (a) Add the following in job step DSNTIRU:

                BIND PACKAGE(DSNJAR) MEMBER(DSNX9LDJ) -
                     ACTION(REPLACE) ISO(CS) CURRENTDATA(YES) -
                     ENCODING(EBCDIC) -
                     LIBRARY('prefix.SDSNDBRM')

                where <prefix> is the high-level qualifier for the
                target DB2 subsystem.

            (b) Add the following GRANT statement in step DSNTIJG

                GRANT EXECUTE ON PACKAGE DSNJAR.DSNX9LDJ TO PUBLIC;

                and optionally change PUBLIC to one or more
                authorization IDs that need to use Java stored
                procedures.

        ----------------------------------------------------------------
        (3) Grant execute access on package DSNX9LDJ
            ***********************************************************
            * All customers who use Java stored procedures need to
            * perform this step.
            ***********************************************************
            Submit a job that contains the following GRANT statement:

                GRANT EXECUTE ON PACKAGE DSNJAR.DSNX9LDJ TO PUBLIC;

            after optionally changing PUBLIC to one or more
            authorization IDs that need to use Java stored procedures.
            The user ID for this job must have authorization to grant
            this authority on the package.

            Note: It is presumed that a package for DSNX9LDJ in
                  collection ID DSNJAR already exists.  If the above
                  GRANT request fails with SQLCODE -204 then
                  submit a job that contains the following BIND
                  statement
1
                BIND PACKAGE(DSNJAR) MEMBER(DSNX9LDJ) -
                     ACTION(REPLACE) ISO(CS) CURRENTDATA(YES) -
                     ENCODING(EBCDIC) -
                     LIBRARY('prefix.SDSNDBRM')

            where <prefix> is the high-level qualifier for the
            target DB2 subsystem.  Then rerun the GRANT statement.
      ACTION:
        ***Action for PM65113 (V10)

        This PTF modifies the DB2 installation CLIST and job DSNTIJSG
        to prevent job step job DSNTIJQ from failing due to SQLCODE -204
        when DSNTIJSG is customized in MIGRATE mode.  If you have
        already installed or migrated to DB2 V10, you need to take the
        following actions after applying this PTF:
        (1) Update customized copies of DB2 installation CLIST members
        (2) Update customized copies of job DSNTIJSG
        These actions are detailed below
        ----------------------------------------------------------------
        (1) Update customized copies of DB2 installation CLIST members
            ***********************************************************
            * This action is required for all V10 customers
            ***********************************************************
            This PTF modifies CLIST members DSNTINST in the
            prefix.SDSNCLST target library only.
            You need to redo any record format changes and reapply any
            tailoring you have done to your private copies of this
            CLIST. You may also want to move it to the
            prefix.NEW.SDSNCLST data set, where the CLISTs processed
            by job DSNTIJVC reside.
        (2) Update customized copies of job DSNTIJSG
            ***********************************************************
            * This action is required only if you ran the DB2 V10
            * installation CLIST in MIGRATE mode
            ***********************************************************
            This PTF modifies DSNTIJSG in the prefix.SDSNSAMP library
            only.  After applying it, edit your customized copy of
            DSNTIJSG and update job step DSNTIJQ as follows:

            (a) Locate and change these lines:
                  //SYSIN    DD  DDNAME=DUMMY
                  //*        DD  DDNAME=CLEANUP
                  //*        DD  DDNAME=CREATE
                  //         DD  DDNAME=CREATENT
                  //DUMMY    DD  *
                to:
                  //SYSIN    DD  DDNAME=DUMMY
                  //*        DD  DDNAME=CLEANUP
                  //         DD  DDNAME=CREATE
                  //*        DD  DDNAME=CREATEPT
                  //         DD  DDNAME=CREATENT
                  //DUMMY    DD  *

            (b) Locate and change these lines:
                    CREATE TABLESPACE DSNOPTTS
1                          IN DSNOPTDB
                           LOCKSIZE ROW
                           LOCKMAX SYSTEM
                           CLOSE NO
                           CCSID UNICODE
                           USING STOGROUP DSNOPTSG;
                    CREATE TABLESPACE DSNOPTT8
                           IN DSNOPTDB
                           BUFFERPOOL BP8K0
                           LOCKSIZE ROW
                           LOCKMAX SYSTEM
                           CLOSE NO
                           CCSID UNICODE
                           USING STOGROUP DSNOPTSG;
                to:
                    CREATE TABLESPACE DSNOPTT8
                           IN DSNOPTDB
                           BUFFERPOOL BP8K0
                           LOCKSIZE ROW
                           LOCKMAX SYSTEM
                           CLOSE NO
                           CCSID UNICODE
                           USING STOGROUP DSNOPTSG;
                //CREATEPT DD  *
                    CREATE TABLESPACE DSNOPTTS
                           IN DSNOPTDB
                           LOCKSIZE ROW
                           LOCKMAX SYSTEM
                           CLOSE NO
                           CCSID UNICODE
                           USING STOGROUP DSNOPTSG;
                (Notice that the order of the two CREATE TABLESPACE
                statements has been reversed).

            (c) Save your changes
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSN@RIN   PM88656
       DSNTESR   PM88656
       DSNTIJSG  PM88656
       DSNTINS1  PM88656
       DSNTRIN   PM88656

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88656   DSN@RIN  DSNTESR  DSNTIJSG DSNTINS1 DSNTRIN

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNTRIN

      MACROS
       DSN@RIN
       DSNTESR
       DSNTIJSG
       DSNTINS1
1
      LISTEND
 UK95721 COVER LETTER END


 UK95726 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM76375 -
        ****************************************************************
        * USERS AFFECTED: DB2 10 for z/OS users of LOB table space     *
        ****************************************************************
        * PROBLEM DESCRIPTION: RC00C90101 DSNOMAPX ERQUAL500A          *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When inserting LOB data bigger than 2M in size, DB2 may
        determine to process the entire LOB data in smaller chunks.
        During insert, if multiple LOB map pages are used then it is
        possible that one or more LOB map pages may not be linked
        correctly.
        DB2 code is modified to ensure LOB map pages are chained
        correctly. Also, the page LRSN value is updated when the
        total lob size is updated and logged on the first LOB map
        page after processing LOB in many smaller chunks.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM76375
    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  PM76375

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM76375   DSNOFLMP

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNOFLMP

      LISTEND
 UK95726 COVER LETTER END


 UK95752 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90152 -
        ****************************************************************
        * USERS AFFECTED: ALL DB2 10 for z/OS users of queries that    *
        *                 contain a SELECT and a GROUPBY with a        *
        *                 DECFLOAT column in an expression.            *
        ****************************************************************
        * PROBLEM DESCRIPTION: An incorrect result (less rows than     *
        *                      expected) can be returned for a query   *
        *                      that contains a SELECT and a GROUPBY    *
1       *                      with a DECFLOAT column in an            *
        *                      expression.                             *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An incorrect result (less rows than expected) can be returned
        for a query with a SELECT and a GROUPBY that contains an
        expression with a DECFLOAT column.

        The following example helps to illustrate the problem.

        Step 1. Create and populate a TABLE T2 that contains a DECFLOAT
                column.

          CREATE TABLE T2(BITRES   DECFLOAT(16));

          INSERT INTO T2 VALUES(2);
          INSERT INTO T2 VALUES(2);
          INSERT INTO T2 VALUES(3);
          INSERT INTO T2 VALUES(4);


        Step 2. Perform the following query with a GROUPBY that contains
                an expression with a DECFLOAT column.

          SELECT T1.LIST FROM
            (SELECT
              CASE BITNOT(BITNOT(BITRES))
                WHEN 2 THEN 'C'
                ELSE 'Z'
              END AS LIST
             FROM T2 ) T1 (LIST)
          GROUP BY T1.LIST;


        Step 3. Check the results.

        The incorrect result is shown as follows.
                   +------+
                   | LIST |
                   +------+
                 1_| C    |
                   +------+

        The correct or expected result is as follows.
                    +------+
                    | LIST |
                    +------+
                  1_| C    |
                  2_| Z    |
                    +------+
        The bindtime code in DB2 has been modified to correct the
        conditions leading to the incorrect result.

        Additional Keywords: SQLGROUPBY SQLINCORR INCORROUT
                             SQLINCORROUT SQLDECFLOAT DB2INCORR/K
1   COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM90152
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM90152:

        See PM90152 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM90152 corrects a problem of incorrect output (less rows
        than expected) when SELECT with GROUPBY with DECFLOAT
        column is in an expression.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM79782:

        See PM79782 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM79782 corrects a problem of ABEND0C4 at DSNXRWND OFFSET 0338
        in DB2 V9 for z/OS or ABEND04E at DSNSVSFB OFFSET 0858 in DB2
        V10 for z/OS.
        To make this fix effective for a static application, it must 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 PM61906:

        See PM61906 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM61906 corrects a problem of ABEND04E at DSNXESX2 when running
        query with COUNT ( DISTINCT (COL) ) and parallelism enabled.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXGSGP  PM90152
       DSNXOSSF  PM90152

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90152   DSNXGSGP DSNXOSSF

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
1      DSNXGSGP
       DSNXOSSF

      LISTEND
 UK95752 COVER LETTER END


 UK95781 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89367 -
        ****************************************************************
        * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
        *                 Specifically those using LOBs or XML and     *
        *                 DRDA encryption is enabled.                  *
        ****************************************************************
        * PROBLEM DESCRIPTION: High enclave CPU utilization occurs     *
        *                      in the DIST address space.              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Normally, LOB/XML data being returned to a client is sent as
        multiple 32767-byte size piece messages.  Each piece of the
        LOB/XML string is retrieved from the database manager and then
        sent to the client.
        However, when a client requests that DRDA data encryption be
        performed on the connection, the entire LOB/XML string must be
        fully materialized into the server agent storage prior to the
        encryption of the data. Once encryption is complete, the data
        is then sent as multiple 32767-byte size piece messages.
        APAR PM79540 was implemented to address a problem with the
        LOB/XML data materialization by first utilizing the entire
        currently allocated send buffer as the initial target of the
        LOB/XML data retrieval.  DB2 would then allocate a larger
        area to hold the fully materialized LOB/XML string if the
        currently allocated send buffer was not large enough.  APAR
        PM79540 introduced a logic error that miscalculated the size
        of area required to hold the fully materialized LOB/XML string.
        Depending on the size of the the LOB/XML data, a condition may
        result where DB2 repeatedly requests the next piece of the
        LOB/XML string from the database manager, hence resulting in
        the DB2 server thread looping indefinitely.
        The server thread will hang as a result of the loop and since a
        DB2 server thread runs under a WLM enclave, excessive enclave
        CPU utilization may be observed in the ssnmDIST address space.

        DB2 has been changed to correctly calculate the size of the
        area required to hold the fully materialized LOB/XML string.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89367
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNLCBFM  PM89367
       DSNLCMSL  PM89367
1      DSNLIINI  PM89367

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89367   DSNLCBFM DSNLCMSL DSNLIINI

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNLCBFM
       DSNLCMSL
       DSNLIINI

      LISTEND
 UK95781 COVER LETTER END


 UK95795 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM67806 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of       *
        *                 dynamic statement cache.                     *
        ****************************************************************
        * PROBLEM DESCRIPTION: Abend ABND04E RC00E2000C may occur at   *
        *                      DSNXODMH DSNSVSVB +0AC2 if dynamic      *
        *                      statement cache is used when            *
        *                      preparing an SQL statement.             *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Abend ABND04E RC00E2000C may occur at DSNXODMH DSNSVSVB +0AC2
        if dynamic statement cache is used when preparing an SQL
        statement.

        The abend occurs because DB2 run out of storage when dynamic
        statement cache is enabled.

        In this apar, a new field QW0225DMH is added to statistics
        record IFCID225. This field tracks the accumulated statement
        dependency (DMHE) storage for statement in the dynamic
        statement cache.
        DB2 was fixed to allow more storage to be allocated
        for the dynamic statement cache.

        Additional Keywords: SQLDYNSTMTCACHE  SQLSTOR
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM67806
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        ***Action for PM67806:

        This PTF adds an online-changeable subsystem parameter in
        DSN6SPRM called CACHE_DEP_TRACK_STOR_LIM that specifies the
        amount of storage in gigabytes that DB2 will allocate for
1       hashing entries in the dynamic statement cache.  Valid setting
        are integers in the range of 2 to 10.  The default is 2.

        If you have already installed or migrated to this version of DB2
        you need to take the following actions after applying this PTF:

        (1) Update customized copies of DB2 installation CLIST members
        (2) Update your customized copy of job DSNTIJUZ
        (3) Update private copies of the DSNTIDxx CLIST input member

        Detailed guidance for these actions follows:

        ----------------------------------------------------------------
        (1) Update customized copies of DB2 installation CLIST members
        ==> This action is required for all customers

            This PTF modifies CLIST member DSNTINST in the SDSNCLST
            target library only. You need to redo any record format
            changes and reapply any tailoring you have done to your
            copies of this CLIST. You may also want to move it to the
            prefix.NEW.SDSNCLST data set, where the CLISTs processed by
            job DSNTIJVC reside.
        ----------------------------------------------------------------
        (2) Update your customized copy of job DSNTIJUZ
        ==> This action is required for all customers

            This PTF modifies DB2 installation job DSNTIJUZ in the
            SDSNSAMP target library. After applying this PTF, you
            need to update your customized copy of this job as follows:

            * Add the keyword parameter CACHE_DEP_TRACK_STOR_LIM=<x>,
              where <x> is an integer from 2 to 10, to the invocation
              of the DSN6SPRM macro.  Make sure to add a continuation
              character in column 72 if needed.  If you omit adding
              CACHE_DEP_TRACK_STOR_LIM here, the value will be set to
              the default of 2 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 CACHE_DEP_TRACK_STOR_LIM 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:

        CACHE_DEP_TRACK_STOR_LIM NUM   M  2           10            <x>

             Change <x> to the value you specified for
1            CACHE_DEP_TRACK_STOR_LIM in step (2), above.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSN@XAZP  PM67806
       DSNDQWPZ  PM67806
       DSNDQW03  PM67806
       DSNDSPRM  PM67806
       DSNLTMSC  PM67806
       DSNTIDXA  PM67806
       DSNTIDXB  PM67806
       DSNTIJUZ  PM67806
       DSNTINST  PM67806
       DSNTXAZP  PM67806
       DSNTXSTB  PM67806
       DSNVMON   PM67806
       DSNWZIFA  PM67806
       DSNWZIF9  PM67806
       DSNXODMH  PM67806
       DSN6SPRM  PM67806

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM67806   DSN@XAZP DSNDQWPZ DSNDQW03 DSNDSPRM DSNLTMSC DSNTIDXA
                 DSNTIDXB DSNTIJUZ DSNTINST DSNTXAZP DSNTXSTB DSNVMON
                 DSNWZIFA DSNWZIF9 DSNXODMH DSN6SPRM

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNLTMSC
       DSNTXAZP
       DSNTXSTB
       DSNVMON
       DSNWZIFA
       DSNWZIF9
       DSNXODMH

      MACROS
       DSN@XAZP
       DSNDQWPZ
       DSNDQW03
       DSNDSPRM
       DSNTIDXA
       DSNTIDXB
       DSNTIJUZ
       DSNTINST
       DSN6SPRM

      LISTEND
 UK95795 COVER LETTER END


 UK95804 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90055 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS       *
1       *                 users of RUNSTATS and STOSPACE utilities     *
        *                 collecting SPACE statistics.                 *
        ****************************************************************
        * PROBLEM DESCRIPTION: INCORROUT SPACEF in MSGDSNU613I and     *
        *                      MSGDSNU614I for table spaces            *
        *                      greater than 2 TB.                      *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        When the user executed RUNSTATS on a LOB TABLESPACE
        with a size greater than 2 TB, the SPACE statistics
        reported in DSNU613I and DSNU614I were incorrect.
        The catalog tables SYSIBM.SYSTABLEPART, SYSIBM.SYSTABLES
        and SYSIBM.SYSTABLESPACE were updated with incorrect
        SPACE statistics.
        The same error occurs with STOSPACE utility as well.
        The error was caused by an overflow of an integer variable
        defined internally to store the space value.
        Code was modified to use larger variables
        that can contain space statistics for objects
        with size greater than 2 TB.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM90055
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUGSPC  PM90055
       DSNUSEOF  PM90055
       DSNUSUIP  PM90055
       DSNUSUTP  PM90055
       DSNUTSSA  PM90055

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90055   DSNUGSPC DSNUSEOF DSNUSUIP DSNUSUTP DSNUTSSA

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUGSPC
       DSNUSEOF
       DSNUSUIP
       DSNUSUTP
       DSNUTSSA

      LISTEND
 UK95804 COVER LETTER END


 UK95806 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM91930 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for zOS users.                    *
        ****************************************************************
1       * PROBLEM DESCRIPTION: AE PM80779 fix completion               *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        AE PM80779 fix completion
        AE PM80779 fix completion
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM91930
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        APAR PM45561 fixes a problem that causes incorrect output for
        readers of XML data that use ISOLATION LEVEL(UR) and
        and potentially allows DB2 to cause the readers of XML data to
        wait for a lock, even though ISO(UR) is specified.
        The situation usually occurs during heavy concurrent insert,
        update, or delete activity.
        The incorrect output problem is fixed by requiring ISOLATION(UR)
        readers to wait for XML locks. As a result, ISOLATION(UR)
        readers that access XML data might see increased wait time for
        locks.
        The additional wait time for unconditional locks sometimes
        result in deadlocks or timeouts(SQLCODE -911 or -913),therefore,
        application logic may need to change to accommodate SQLCODEs
        -911 and -913.
      ACTION:
        TYPE:  DB2

        This fix corrects a problem with Compensation Log Records
        (CLRs) built for compression dictionary pages for classic
        (non-segmented) partitioned table spaces during insert.

        The problem is limited to classic partitioned table spaces that
        have an insert-generated compression dictionary and have been
        RECOVERED with log-apply. A dictionary page log record may not
        get applied correctly due to incorrect DBID/OBID, which happens
        under limited circumstances.

        Compression dictionaries built by DB2 LOAD or DB2 REORG are not
        affected. You can identify an insert-generated dictionary by
        checking the HPGZLD field in the page header of the header-page
        of each pageset/partition. HPGZLD would be = 'F' for an
        insert-generated dictionary.

        The symptoms of the problem include abends and/or error return
        codes in/from modules that try to use the dictionary pages,
        and/or DSNT501I RESOURCE UNAVAILABLE messages on the console
        with DB2 reason code = 00C9007F.

        The fix will correct the problem but it will not correct the
        log records already written with the error. So, after applying
        the fix, establishing new recovery bases for the table spaces
        which have the conditions specified above is advised. Forward
        log apply processes for such table spaces should not be
        performed against image copies taken prior to the application
1       of the fix.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNILSTS  PM91930

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM91930   DSNILSTS

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNB1CLM
       DSNB1CNE
       DSNB1CPS
       DSNB1DCM
       DSNB1DDN
       DSNB1DRA
       DSNB1LCM
       DSNB1LDA
       DSNB1LDN
       DSNB1OPL
       DSNB1OPP
       DSNB1OPS
       DSNB1PMT
       DSNB1PM2
       DSNB1POC
       DSNB1RCM
       DSNB1RRR
       DSNB1WFO
       DSNB5RAP
       DSNGDCOB
       DSNIACCH
       DSNIADR
       DSNICABS
       DSNICHLK
       DSNICLPM
       DSNICMT2
       DSNICPOS
       DSNICREL
       DSNICRFT
       DSNICSEC
       DSNICTAC
       DSNICUMW
       DSNIDILS
       DSNIDLER
       DSNIESEN
       DSNIFDPO
       DSNIHDUP
       DSNIHSET
       DSNIIEPL
       DSNILCLO
       DSNILKES
       DSNILREP
       DSNILSMG
       DSNILSTS
       DSNIMNEX
1      DSNIMSAR
       DSNIMSCU
       DSNIMSRI
       DSNIMS1W
       DSNIONXP
       DSNIONX2
       DSNIOST2
       DSNIOW
       DSNIOWRE
       DSNIPOCH
       DSNIPOCR
       DSNIPOSP
       DSNIPOSS
       DSNIRDCU
       DSNIRELD
       DSNIRELK
       DSNIRELS
       DSNIRELU
       DSNIRFNX
       DSNIRIDL
       DSNIRNXT
       DSNIRPRE
       DSNIRPRV
       DSNIRRCU
       DSNIRSET
       DSNIRSVP
       DSNISELL
       DSNISFRL
       DSNISFS
       DSNISFX2
       DSNISGFO
       DSNISGRT
       DSNISHPI
       DSNISMEX
       DSNISMRT
       DSNISNPG
       DSNISRID
       DSNISRTI
       DSNISUPI
       DSNISVPT
       DSNITCUS
       DSNITDLE
       DSNIXLDI
       DSNIZLDL
       DSNKCKOP
       DSNKDLE
       DSNKFLRR
       DSNKFLST
       DSNKFPRV
       DSNKFTCH
       DSNKFTRR
       DSNKINSL
       DSNKISPL
       DSNKMSAX
       DSNKNXT2
       DSNKPOSI
1      DSNKUNR2
       DSNNOLCK
       DSNOALLO
       DSNOCHLO
       DSNODCRL
       DSNOFRLC
       DSNOLDEL
       DSNOTCSO
       DSNTSTRT
       DSNUKIFK
       DSNUKNFK
       DSNUULXA

      LISTEND
 UK95806 COVER LETTER END


 UK95825 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM87153 -
        ****************************************************************
        * USERS AFFECTED: DB2 users.                                   *
        ****************************************************************
        * PROBLEM DESCRIPTION: When running certain utilities, DB2     *
        *                      will create SYSLGRNX entries for COPY   *
        *                      NO indexes.  Since these will not be    *
        *                      used for recovery or anything else,     *
        *                      they're just wasting space.             *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When a table space or index is modified by a non-logging utility
        such as REBUILD, a "dummy" SYSLGRNX entry is created with the
        same starting and ending LRSN.  These should not be created for
        COPY NO indexes, but this was overlooked when the code was
        reworked for DB2 V9.
        The code which creates the "dummy" SYSLGRNX entries after a
        non-logging utility has been modified to skip it for COPY NO
        indexes.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM87153
    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  PM87153
       DSNB1CPP  PM87153
       DSNB1PCP  PM87153

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM87153   DSNB1CPL DSNB1CPP DSNB1PCP

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
1      DSNB1CPL
       DSNB1CPP
       DSNB1PCP

      LISTEND
 UK95825 COVER LETTER END


 UK95830 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM87554 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 9 and 10 for z/OS who use   *
        *                 IBM DB2 Analytics Accelerator (IDAA).        *
        ****************************************************************
        * PROBLEM DESCRIPTION: IFCID 3 accounting records are not      *
        *                      written on transaction boundaries       *
        *                      for distributed DataBase Agent Threads  *
        *                      (DBATs) that service queries that are   *
        *                      offloaded to IDAA.                      *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        A remote application connects to a DB2 for z/OS server and
        executes queries that qualify to be offloaded to IDAA.  Due to
        the IDAA involvement, the DBAT that services the query remains
        active.  As a result, DB2 accounting data is not available
        until the connection is terminated and hence the DBAT
        deallocates.
        For long running DBATs, this presents a usability issue as it
        is difficult to understand how the application is performing
        and behaving.

        DB2 for z/OS has been changed to support transaction level
        accounting for distributed threads (DBATs) that service
        IDAA requests, regardless if the DBAT remains active.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM87554
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNLEDDA  PM87554
       DSNLQCTL  PM87554
       DSNTACT   PM87554
       DSNTXSTB  PM87554
       DSNWVZSA  PM87554
       DSNX8SMF  PM87554

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM87554   DSNLEDDA DSNLQCTL DSNTACT  DSNTXSTB DSNWVZSA DSNX8SMF

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
1      DSNLEDDA
       DSNLQCTL
       DSNTACT
       DSNTXSTB
       DSNWVZSA
       DSNX8SMF

      LISTEND
 UK95830 COVER LETTER END


 UK95832 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM78128 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2.                            *
        ****************************************************************
        * PROBLEM DESCRIPTION: NEW DB2 z/OS for V10R1 FUNCTION SUPPORT *
        *                      FOR END OF RESTART AUTOMATIC LPL        *
        *                      RECOVERY.                               *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Prior to this APAR, auto-LPL function was supported only during
        DB2 mainline operation. However, with this APAR, LPL recovery
        will automatically be triggered, at the end of DB2 restart, for
        the objects that were added to LPL during the restart. This will
        avoid or minimize any application failures due to object in LPL.
        This auto-LPL recovery will not be triggered if (1) the object
        is ZPARM deferred (2) DB2  started in maintenance mode (3) DB2
        started by RESTORE SYSTEM Utility (4) object is associated with
        either indoubt or postponed abort transaction.
          The end of restart LPL recovery
        logic is the same as today's mainline LPL recovery logic. i.e.
        it will issue existing LPL/GRECP recovery messages to indicate
        the start and end of LPL recovery of each object.
          The auto-LPL recovery, if needed, will also be
        triggered at the end of Restart Light. This way DB2 will
        automatically recover as many LPL objects are possible before
        DB2 is terminated after it was started in Light mode.
        This new function will trigger auto-LPL recovery at the end of
        restart, whenever the object is added to LPL by restarting DB2
        member.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM78128
    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  PM78128
       DSNB1LPL  PM78128
       DSNIAGBR  PM78128
       DSNIERST  PM78128
       DSNIIMPD  PM78128
       DSNTRSTE  PM78128
1      DSNXERST  PM78128

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM78128   DSNB1CPP DSNB1LPL DSNIAGBR DSNIERST DSNIIMPD DSNTRSTE
                 DSNXERST

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNB1CPP
       DSNB1LPL
       DSNIAGBR
       DSNIERST
       DSNIIMPD
       DSNTRSTE
       DSNXERST

      LISTEND
 UK95832 COVER LETTER END


 UK95836 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90953 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 UDB for z/OS Version 9      *
        *                 ODBC/CLI and DB2 10 for z/OS ODBC/CLI.       *
        ****************************************************************
        * PROBLEM DESCRIPTION: When an ODBC application performs a     *
        *                      multi-row fetch using SQLExtendedFetch  *
        *                      for rowsets larger than 32K, users      *
        *                      may experience unexpected performance   *
        *                      degradation.                            *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When SQLExtendedFetch() is called for multi-row fetch with
        a rowset greater then 32k, an application can experience
        performance degradation because a single row fetch is
        incorrectly executed when the SQL_ATTR_ROWSET_SIZE
        statement attribute is not set correctly.

        When SQLSetStmtAttr() is called to set SQL_ATTR_ROWSET_SIZE
        with a value greater than 32k, it should set the actual
        rowset size to the maximum value of 32767 and return a
        SQLCODE of SQL_SUCCESS_WITH_INFO with SQLSTATE 01S02.

        ODBC was instead accepting the greater than 32k rowset value
        which caused a single-row fetch to occur rather than the
        expected multi-row fetch which resulted in the observed
        performance degradation.
        Code has been changed so that SQLSetStmtAttr() will correctly
        handle the setting of SQL_ATTR_ROWSET_SIZE to values greater
        than 32k correctly.
    COMPONENT:  5740-XYR02-JDBAA17
    APARS FIXED: PM90953
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
       DSNAOG0O  PM90953
       DSNAOCLI  PM90953
       DSNAOSDK  PM90953

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90953   DSNAOG0O DSNAOCLI DSNAOSDK

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNAOG0O
       DSNAOCLI

      MACROS
       DSNAOSDK

      LISTEND
 UK95836 COVER LETTER END


 UK95853 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90151 -
        ****************************************************************
        * USERS AFFECTED: DB2 users of stored procedures and           *
        *                 User Defined Functions (UDFs).               *
        ****************************************************************
        * PROBLEM DESCRIPTION: In the case where a stored procedure    *
        *                      spawns a thread and the spawned thread  *
        *                      calls another stored procedure, the     *
        *                      inner stored procedure can be queued    *
        *                      in WLM for longer than the STORTIME     *
        *                      zparm value leading to a sqlcode471     *
        *                      rc00E79002.                             *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        In the case where a stored procedure spawns a thread
        and the spawned thread calls another stored procedure,
        the inner stored procedure can exceed the STORTIME zparm.
        This can occur if WLM needs to start an additional server
        asid to satisfy the request.
        With the change in this apar, DB2 will now use the
        DEPENDENT(YES) attribute when inserting the WLM request
        to schedule the stored procedure. Provided there are system
        resources available, WLM will give increased priority to
        this request. This should help prevent the sqlcode471
        rc00E79002.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM90151
    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
       DSNX9GPL  PM90151

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90151   DSNX9GPL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNX9GPL

      LISTEND
 UK95853 COVER LETTER END


 UK95879 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86693 -
        ****************************************************************
        * USERS AFFECTED: DB2 10 for z/OS users using index insert I/O *
        *                 parallelism.                                 *
        ****************************************************************
        * PROBLEM DESCRIPTION: When user uses -SET SYSPARM command to  *
        *                      change the subsystem parameter          *
        *                      INDEX_IO_PARALLELISM online, the        *
        *                      change does not take effect until       *
        *                      the table space is closed and           *
        *                      reopened.                               *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The subsystem parameter INDEX_IO_PARALLELISM is an online
        changeable zparm, but when user uses -SET SYSPARM command to
        change this zparm online, the change does not take effect until
        the table space is closed and reopened.

        Due to the zparm not taking effect immediately, the application
        may not perform as well as expected.
        DB2 code has been modified to make subsystem parameter
        INDEX_IO_PARALLELISM online changeable. After user uses
        -SET SYSPARM command to change the subsystem parameter
        INDEX_IO_PARALLELISM, the next SQL INSERT statement
        will start to use the new value.

        Additional keywords: SQLINSERT
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM86693
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNISRTI  PM86693
1
      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM86693   DSNISRTI

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNISRTI

      LISTEND
 UK95879 COVER LETTER END


 UK95893 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM80017 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS V9.1, and                   *
        *                 DB2 for z/OS V10 users of the                *
        *                 IFCID flat file (DSNWMSGS).                  *
        ****************************************************************
        * PROBLEM DESCRIPTION: DSNWMSGS needs to be udpated to         *
        *                      reflect changes since the               *
        *                      beginning of 2013.                      *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Updates to the IFCID flat file (DSNWMSGS) since the beginning
        of 2013 are needed for all supported DB2 for z/OS versions.
        This APAR delivers updates to the IFCID flat file (DSNWMSGS)
        for the following DB2 for z/OS versions:
        - DB2 for z/OS V9.1
        - DB2 for z/OS V10
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM80017
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNWMSGS  PM80017

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM80017   DSNWMSGS

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MACROS
       DSNWMSGS

      LISTEND
 UK95893 COVER LETTER END


 UK95915 COVER LETTER START
    PROBLEM DESCRIPTION(S):
1     PM87082 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users *
        *                 of tracker site.                             *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C90101 at DSNIBHRE:5006    *
        *                      during RECOVER TABLESPACE               *
        *                      DSNDB06.SYSCOPY LOGONLY on tracker site *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available.         *
        ****************************************************************
        ABEND04E RC00C90101 at DSNIBHRE ERQUAL5006 happened during a
        RECOVER TABLESPACE DSNDB06.SYSCOPY LOGONLY on a tracker site
        because a previously run RECOVER job inserted a record with
        ICTYPE='E' into SYSIBM.SYSCOPY.

        RECOVER utility should not insert SYSCOPY records on tracker
        site.
        RECOVER utility has been modified not to insert SYSCOPY records
        on tracker site.

        Additional Keywords: DSN6SPRM TRKRSITE=YES
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM87082
    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  PM87082

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM87082   DSNUCATM

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUCATM

      LISTEND
 UK95915 COVER LETTER END


 UK95923 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89798 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 and 11 for z/OS users of an       *
        *                 SQL statement that contains multiple         *
        *                 outer joins.                                 *
        ****************************************************************
        * PROBLEM DESCRIPTION: Incorrect output could happen for an    *
        *                      SQL statement that satisfies all of the *
        *                      following conditions:                   *
        *                                                              *
        *                      1. It contains multiple outer joins;    *
1       *                      2. It contains a table expression that  *
        *                         referencing a column out side of the *
        *                         table expression.                    *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An example is shown below:

        CREATE TABLE T1 ( C1 CHAR(4), C2 CHAR(4), C3 CHAR(4));
        CREATE TABLE T2 ( C1 CHAR(4), C2 CHAR(4), C3 CHAR(4));
        COMMIT;

        SELECT T1.C3
        FROM T1 AS T11 LEFT OUTER JOIN T2
                ON T1.C2=T2.C2
             LEFT OUTER JOIN TABLE(
               SELECT T1.C2, T2.C2
               FROM T1 as T12, T2
               WHERE T12.C2 = T11.C2
             ) AS TE(C2, C3)
               ON T11.C2=TE.C2
        GROUP BY T1.C3
        ;

        DB2 did not correctly process the aforementioned SQL statements,
        which caused the incorrect output.
        DB2 has been modified to correctly process the aforementioned
        SQL statement, so there will be no incorrect output.

        Additional keywords: SQLOUTERJOIN SQLFULLJOIN SQLOUTER
                             SQLFULL SQLJOIN SQLTABLEEXPR
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89798
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM89798:

        See PM89798 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM89798 corrects a problem that incorrect output could happen
        for an SQL statement that satisfied all of the following
        conditions:

        1. It contains multiple outer joins;
        2. It contains a table expression that referencing a column out
           side of the table expression.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM74279:
1
        See PM74279 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM74279 corrects a problem of ABEND0C7 at
        DSNXGRDS.DSNXRSBC+8086 or incorrect output could occur
        for an SQL statement that satisfies the following conditions:
        1. contains a scalar fullselect,
        2. the scalar fullselect contains an aggregate function in the
           select list, it involves invalid syntax. SQLCODE -122 is
           expected for this case.

        To make this fix effective for a static application, it must 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 PM74279:
        TYPE:  ACT

        PM74279 corrects a problem of ABEND0C7 at
        DSNXGRDS.DSNXRSBC+8086 or incorrect output could occur
        for an SQL statement that satisfies the following conditions:
        1. contains a scalar fullselect,
        2. the scalar fullselect contains an aggregate function in the
           select list and it involves invalid syntax. SQLCODE -122 is
           expected for this case, but no error message is issued
           and the query completes successfully or abends.

        After the application of this PTF, ALTER PROCEDURE REGENERATE,
        ALTER FUNCTION REGENERATE is required for each native
        SQL procedure or SQL scalar function that contains a scalar
        fullselect statement described as above.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOASG  PM89798
       DSNXODML  PM89798
       DSNXOIN   PM89798
       DSNXOMRG  PM89798
       DSNXOQ2   PM89798

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89798   DSNXOASG DSNXODML DSNXOIN  DSNXOMRG DSNXOQ2

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOASG
       DSNXODML
       DSNXOIN
       DSNXOMRG
       DSNXOQ2

      LISTEND
 UK95923 COVER LETTER END

1
 UK95925 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM78552 -
        ****************************************************************
        * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
        *                 Specifically where DB2 is configured with    *
        *                 DSN6FAC PRIVATE_PROTOCOL=NO and (SNA)        *
        *                 inbound translation is defined relative to   *
        *                 remote DB2 for z/OS requester systems.       *
        ****************************************************************
        * PROBLEM DESCRIPTION: Message DSNL030I, from CSECT DSNLXRAL   *
        *                      or DSNLXALC, with AUTHID=SYSOPR and     *
        *                      REASON=00D3443D.                        *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        A DB2 for z/OS subsystem is configured with (DSNZPARM)
        DSN6FAC PRIVATE_PROTOCOL=NO because the user wants DB2 to
        utilize consistent package authorization behavior regardless
        of the remote requester system platform, DB2 for z/OS or not,
        that's accessing DB2 for z/OS as a server.
        However, if the DB2 for z/OS server is being accessed by a
        remote DB2 for z/OS requester system via SNA and inbound
        translation is defined for the remote requester LU Name
        (SYSIBM.LUNAMES USERNAMES='I'), then access to the DB2 for
        z/OS server will be incorrectly rejected with message
        DSNL030I DSNLX... AUTHID=SYSOPR REASON=00D3443D.
        Note: As a result of the (DSNL030I message) rejection, the
          remote DB2 for z/OS requester system may issue message
          DSNL500I with RTNCD=00 FDBK2=0B RCPRI=0048 RCSEC=0000
          SENSE=080F6051, and the remote DB2 for z/OS application
          will receive SQLCODDE -30080 0048 0000-080F6051 DSNLVRPL.
        To circumvent the condition and allow access, users can
        add a SYSIBM.USERNAMES inbound translation row for AUTHID
        SYSOPR, or the (DSNZPARM) DSN6FAC PRIVATE_PROTOCOL value
        can be changed to a value other than NO.

        DB2 for z/OS server processing, when configured with DSN6FAC
        PRIVATE_PROTOCOL=NO, has been changed to tolerate inbound (SNA)
        access from remote DB2 for z/OS requester systems when inbound
        translation is also defined relative to the requester.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM78552
    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  PM78552
       DSNLXALC  PM78552
       DSNLXRAL  PM78552

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM78552   DSNLTACC DSNLXALC DSNLXRAL

1     THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNLTACC
       DSNLXALC
       DSNLXRAL

      LISTEND
 UK95925 COVER LETTER END


 UK95950 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86696 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users that do not        *
        *                 specify an ISOLATION level on bind package.  *
        ****************************************************************
        * PROBLEM DESCRIPTION: DB2 incorrectly avoids locks when       *
        *                      an ISOLATION level is not specified for *
        *                      BIND PACKAGE and the ISOLATION level    *
        *                      specified on BIND PLAN is RS or RR.     *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        DB2 incorrectly avoids locks when an ISOLATION level is not
        specified for BIND PACKAGE but the ISOLATION level specified as
        a BIND PLAN option is RS (read stability) or RR (repeatable
        read).

        DB2 should lock rows for an ISOLATION level of RS or RR.  If
        however, both of the following are true, DB2 may incorrectly
        avoid obtaining locks (i.e. lock avoidance).

          1. The ISOLATION level is not specified on the BIND PACKAGE
             command.
          2. The ISOLATION level specified on the BIND PLAN is RS or RR.

        The default ISOLATION level is the value specified on BIND PLAN.
        If the ISOLATION level is not specified on BIND PACKAGE or
        BIND PLAN, the default ISOLATION level is CS (cursor stability).


        The following example will help illustrate the problem.

        Step 1. Create a simple table T1 and insert three rows.

          CREATE TABLE T1 (C1 INT);

          INSERT INTO T1 VALUES(1);
          INSERT INTO T1 VALUES(2);
          INSERT INTO T1 VALUES(3);


        Step 2. BIND a package with the following SQL and no ISOLATION
        level (do not specify the ISOLATION level keyword).
1
           SELECT C1 INTO :hv1
           FROM T1
           WHERE C1 = 2;


        Step 3. BIND and execute a PLAN with a specified ISOLATION
        level (RS). During execution, LOCK AVOIDANCE is incorrectly
        employed.

        The code in DB2 has been modified to turn off LOCK AVOIDANCE for
        ISO(RS) and ISO(RR) isolation levels during execution of the
        package.

        Additional Keywords: SQLISOLATION SQLLOCK SQLBIND
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM86696
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXEBR   PM86696
       DSNXRPUF  PM86696

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM86696   DSNXEBR  DSNXRPUF

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXEBR
       DSNXRPUF

      LISTEND
 UK95950 COVER LETTER END


 UK95953 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88456 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users *
        *                 of REORG SHRLEVEL CHANGE.                    *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C4 RC4 at DSNURBXA + x'657C'      *
        *                      happened during a REORG SHRLEVEL CHANGE *
        *                      on a segmented table space.             *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available.         *
        ****************************************************************
        A REORG SHRLEVEL CHANGE was run against a segmented table space.
        A subtask started to BUILD the clustering index while the main
        task was still in RELOAD phase. ABENDS0C4 RC4 at DSNURBXA
        OFFSET657C occurred because the subtask used a pointer that was
        cleared by the main task COMMIT processing.
1
        A similar problem can also happen for non-segmented table
        spaces.
        REORG SHRLEVEL CHANGE has been modified to use correct pointers
        in the BUILD phase.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88456
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNURBXA  PM88456

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88456   DSNURBXA

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNURBXA

      LISTEND
 UK95953 COVER LETTER END


 UK95971 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86652 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 9 and 10 for z/OS.          *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C4 in CSECT DSNVXLT0 after        *
        *                      issuing a -DISPLAY BPOOL command with   *
        *                      BPOOL parameter consisting of all       *
        *                      spaces. Subsystem termination with      *
        *                      reason code RC00C200D3 followed.        *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        DB2 command parser incorrectly handles the case when a keyword
        parameter consists entirely of spaces, passing along an
        incorrect parameter. This may cause issues for various DB2
        components that may rely on DB2 command processor to validate
        parameter input and in the case of -DIS BPOOL command resulted
        in an ABEND0C4 causing subsystem termination.
        Corrected the command parser to properly handle parameters
        consisting of empty spaces.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM86652
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSN9SCN1  PM86652
1
      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM86652   DSN9SCN1

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSN9SCN1

      LISTEND
 UK95971 COVER LETTER END


 UK95978 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM91902 -
        ****************************************************************
        * USERS AFFECTED: All data sharing users of DB2 for zOS.       *
        ****************************************************************
        * PROBLEM DESCRIPTION: DB2 restart can hang when re-enabling   *
        *                      data sharing mode, and deactivated or   *
        *                      destroyed members of the data sharing   *
        *                      group exist.                            *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        During the data sharing REENABLE process, DB2 restart of the
        surviving member will issue WTORs to restart the other members
        of the group, or to reply QUIESCED.  End Restart will suspend
        in DSNRRGRT waiting for all the restarting members to complete
        their restart checkpoint, but does not account for deactivated
        or destroyed members.
        DSNRRGRC processing has been corrected so that DSNRRGRT will no
        longer wait for deactivated or destroyed members of the data
        sharing group to restart when re-enabling data sharing mode.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM91902
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNRRGRC  PM91902

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM91902   DSNRRGRC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNRRGRC

      LISTEND
 UK95978 COVER LETTER END


1UK96041 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM91422 -
        ****************************************************************
        * USERS AFFECTED: All data sharing users of DB2 for zOS.       *
        ****************************************************************
        * PROBLEM DESCRIPTION: During group restart, MSGDSNR058I       *
        *                      will not be issued when waiting for     *
        *                      an archive log data set doing restart   *
        *                      recovery for a peer member of a data    *
        *                      sharing group.                          *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        During restart, a timer task will issue MSGDSNR055I if
        restart has remained suspended across a 2 minute interval.
        If the suspend is for the recall or tape mount for an
        archive log data set, MSGDSNR058I should be issued
        providing the archive log data set name.  If restart is
        doing recovery for a peer member of the data sharing
        group, control block addressability is not correct which
        prevents the DSNR058I message from being issued.
        Control block addressability has been corrected in DSNRTIMR
        for peer member restart recovery.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM91422
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNRTIMR  PM91422

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM91422   DSNRTIMR

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNRTIMR

      LISTEND
 UK96041 COVER LETTER END


 UK96043 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM87136 -
        ****************************************************************
        * USERS AFFECTED: All DB2 users who alter a partitioned table  *
        *                 space buffer pool, the table space           *
        *                 is created with LARGE or DSSIZE keyword,     *
        *                 or NUMMPART>=65 and there are partitioned    *
        *                 indexes on the table space.                  *
        ****************************************************************
        * PROBLEM DESCRIPTION: After alter the table space buffer pool *
1       *                      customer may receive the following      *
        *                      REAPIR DBD errors,                      *
        *                                                              *
        *                      DSNU901I DSNUEDDR - OBD X'0053' AN      *
        *                      INDEX PAGESET OBD HAS THE FOLLOWING     *
        *                      DIFFER                                  *
        *                      ....                                    *
        *                      DSNU920I DSNUEDPS - OBDS DIFFER AT      *
        *                      OFFSET X'0000004C' OBDPSIZE             *
        *                      DSNU904I DSNUEDPS - EXISTING VALUE      *
        *                                          X'0019'             *
        *                      DSNU905I DSNUEDPS - REBUILT  VALUE      *
        *                                          X'0018'             *
        *                                                              *
        *                      DSNU920I DSNUEDPS - OBDS DIFFER AT      *
        *                      OFFSET X'000000C8' OBDPSRPG(2)          *
        *                      DSNU904I DSNUEDPS - EXISTING VALUE      *
        *                                          X'02000002'         *
        *                      DSNU905I DSNUEDPS - REBUILT VALUE       *
        *                                          X'01000002'         *
        *                      DSNU920I DSNUEDPS - OBDS DIFFER AT      *
        *                      OFFSET X'00000108' OBDPSRPG(3)          *
        *                      DSNU904I DSNUEDPS - EXISTING VALUE      *
        *                                          X'04000002'         *
        *                      DSNU905I DSNUEDPS - REBUILT VALUE       *
        *                                          X'02000002'         *
        *                      DSNU920I DSNUEDPS - OBDS DIFFER AT      *
        *                      OFFSET X'00000148' OBDPSRPG(4)          *
        *                      DSNU904I DSNUEDPS - EXISTING VALUE      *
        *                                          X'06000002'         *
        *                      DSNU905I DSNUEDPS - REBUILT VALUE       *
        *                                          X'03000002'         *
        *                      DSNU920I DSNUEDPS - OBDS DIFFER AT      *
        *                      OFFSET X'00000188' OBDPSRPG(5)          *
        *                      DSNU904I DSNUEDPS - EXISTING VALUE      *
        *                                          X'08000002'         *
        *                      DSNU905I DSNUEDPS - REBUILT VALUE       *
        *                                          X'04000002'         *
        *                      DSNU913I DSNUEDDR - OBD X'0053'         *
        *                      COMPARISON COMPLETE -- 5 ERRORS WERE    *
        *                      FOUND                                   *
        *                                                              *
        *                      DSNU901I DSNUEDDR - OBD X'0054' AN      *
        *                      INDEX FANSET OBD HAS THE FOLLOWING      *
        *                      DIFFERE                                 *
        *                      ...                                     *
        *                                                              *
        *                      DSNU920I DSNUEDFT - OBDS DIFFER AT      *
        *                      OFFSET X'00000052' OBDINNUM             *
        *                      DSNU904I DSNUEDFT - EXISTING VALUE      *
        *                                          X'0080'             *
        *                      DSNU905I DSNUEDFT - REBUILT VALUE       *
        *                                          X'0100'             *
        *                      DSNU920I DSNUEDFT - OBDS DIFFER AT      *
        *                      OFFSET X'00000054' OBDINSHF             *
        *                      DSNU904I DSNUEDFT - EXISTING VALUE      *
1       *                                          X'19'               *
        *                      DSNU905I DSNUEDFT - REBUILT VALUE       *
        *                                          X'18'               *
        *                      DSNU913I DSNUEDDR - OBD X'0054'         *
        *                      COMPARISON COMPLETE -- 2 ERRORS WERE    *
        *                      FOUND                                   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When the table space buffer pool is changed, the OBDs of the
        partitioned index on the table space could be affected.
        However, alter the buffer pool does not update the partitioned
        index OBDs, which causes the above repair DBD errors.
        DB2 has been changed to update partitioned index OBDs when
        the table space buffer pool is altered.

        Applying the apar does not fix the OBDs which are already
        broken. The incorrect OBDs could be fixed by drop and recreate
        the indexes.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM87136
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNGDADP  PM87136
       DSNGDAIP  PM87136

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM87136   DSNGDADP DSNGDAIP

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNGDADP
       DSNGDAIP

      LISTEND
 UK96043 COVER LETTER END


 UK96045 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM87970 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users who rebind a plan  *
        *                 that was bound before V10 from a DBRM and    *
        *                 have the zparm DISALLOW_DEFAULT_COLLID set   *
        *                 to ON.                                       *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00E2000D occurs for a REBIND *
        *                      PLAN if the following conditions are    *
        *                      true.                                   *
        *                      1. The current plan was bound before    *
        *                         V10 from a DBRM.                     *
1       *                      2. The zparm DISALLOW_DEFAULT_COLLID is *
        *                         set to ON.                           *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        ABEND04E RC00E2000D occurs for a REBIND PLAN when the plan was
        previously bound before V10 from a DBRM and the zparm
        DISALLOW_DEFAULT_COLLID is set to ON. When this zparm is set ON,
        DB2 fails the REBIND PLAN, but does not mark this case properly.
        Thus abend occurs when cleaning up space for the error case.

        Additional Keywords:
        ABEND04E RC00E2000D
        Code has been changed to mark the error case and clean up the
        space correctly.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM87970
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        See PM43078 APAR/PTF text in the PTF cover letter for
        additional information about why REBIND PLAN is necessary.

        PM43078 fixes an unexpected SQLCODE -104 during REBIND PLAN in
        DB2 V10 NFM mode, or SQLCODE -924 with reason code 00E30302
        during execution in V10 NFM mode if the PLAN is bound directly
        with DBRMs in DB2 V8.

        To make this fix effective for plans already been executed once,
        a REBIND PLAN is required after application of this PTF.
        Review the PTF cover letter to determine which, if any, plans
        could be affected by this change.
      ACTION:
        Since the problem that occurred could leave incorrect SYSENTRIES
        values in SYSIBM.SYSPACKAGE table, if you discover the number
        in the SYSENTRIES column for a package does not match the number
        of entries in SYSIBM.SYSPKSYSTEM, you will need to manually
        correct the SYSENTRIES column. Please contact IBM Service for
        assistance in correcting those records.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNTBCM6  PM87970

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM87970   DSNTBCM6

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNTBCM6

      LISTEND
 UK96045 COVER LETTER END


1UK96055 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM78856 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of XML columns     *
        *                 that support multiple XML versions.          *
        ****************************************************************
        * PROBLEM DESCRIPTION: When there are many deletes or updates  *
        *                      on an XML column that supports multiple *
        *                      XML versions, significant I/O on the    *
        *                      XML Node ID index was caused by the     *
        *                      XMLCLN asynchronous SRB that deletes    *
        *                      unneeded XML rows.                      *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Significant I/O and GetPages were caused by the XMLCLN
        asynchronous SRB that deletes unneeded XML rows from the
        XML table space.  The problem was the search criteria used
        on the XML Node ID index included too many unnecessary pages.
        This problem only occurs when the XML column supports multiple
        XML versions.  The problem is more likely to occur when there
        are a large number of deletes or updates on the XML column.
        The search criteria for the XML Node ID index that's used by
        the XMLCLN asynchronous SRB is improved to reduce the number
        of I/O and the number of GetPages.

        Additional keywords: XMLALL
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM78856
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNNOCLN  PM78856
       DSNNOEXP  PM78856
       DSNNOWRT  PM78856
       DSNNXCMT  PM78856
       DSNNXDLC  PM78856

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM78856   DSNNOCLN DSNNOEXP DSNNOWRT DSNNXCMT DSNNXDLC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNNOCLN
       DSNNOEXP
       DSNNOWRT
       DSNNXCMT
       DSNNXDLC

      LISTEND
 UK96055 COVER LETTER END

1
 UK96056 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88663 -
        ****************************************************************
        * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
        *                 Specifically those where DB2 is accessed     *
        *                 (as a server) via TCP/IP connections from    *
        *                 remote CICS or IMS based DB2 for z/OS        *
        *                 applications.                                *
        ****************************************************************
        * PROBLEM DESCRIPTION: Unrealistic SMF 101 record elapsed      *
        *                      times due to incorrect QWAC related     *
        *                      values, such as QWACBSC, QWACBJST,      *
        *                      and QWACASC.                            *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When a DB2 for z/OS server thread is reused, on behalf of a new
        user of a remote CICS or IMS based DB2 for z/OS application,
        accounting processing is necessary to reflect the end of
        activity related to the prior user and the beginning of
        activity related to the new user. When the connection to the
        DB2 for z/OS server is via TCP/IP, this accounting transition
        may not occur which may ultimately lead to incorrect QWAC
        accounting values.

        DB2 (DDF processing) has been changed to ensure that proper
        accounting transitioning will occur.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88663
    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  PM88663

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88663   DSNLTEXC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNLTEXC

      LISTEND
 UK96056 COVER LETTER END


 UK96072 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90484 -
        ****************************************************************
        * USERS AFFECTED: DB2 10 for z/OS users who try to alter       *
        *                 a procedure/function between two invocations *
1       *                 of the procedure/function.                   *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C6 RC06 DSNILREP can occur on an  *
        *                      SQL procedure/function if it is invoked *
        *                      then altered and invoked again in the   *
        *                      same commit scope.                      *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        ABEND0C6 RC06 DSNILREP can occur on an SQL procedure/function if
        it is invoked then altered and invoked again in the same commit
        scope. The reason is the cached code for the procedure/function
        is not purged after the ALTER PROCEDURE/FUNCTION.

        Additional Keywords:
        ABEND0C6 RC00000006 SQLUDF SQLSTOREDPROC SQLSP SQLALTER
        SQLCODE615
        Code has been changed so the ALTER PROCEDURE/FUNCTION is blocked
        if it follows the invocation of the procedure/function in the
        same commit scope.  SQLCODE -615 is issued in this case.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM90484
    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  PM90484

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90484   DSNTBRB2

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNTBRB2

      LISTEND
 UK96072 COVER LETTER END


 UK96085 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89035 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 10 for z/OS.                *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00E2000C detected when       *
        *                      issuing a command requiring             *
        *                      authorization.                          *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        A storage shortage may be detected by a request using a command
        requiring authorization checking. In some instances, these
        requests do not free storage obtained from global storage pools
1       leading to a slow storage leak over time.
        Deallocation has been modified to clean up storage for
        global pools.

        ADDITIONAL KEYWORDS: DB2STGLK/K
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89035
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNSVSFB  PM89035
       DSNSVSPP  PM89035
       DSNTADL   PM89035

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89035   DSNSVSFB DSNSVSPP DSNTADL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNSVSFB
       DSNSVSPP
       DSNTADL

      LISTEND
 UK96085 COVER LETTER END


 UK96107 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM92612 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS      *
        *                 users of queries which contain an            *
        *                 OLAP function and select list that           *
        *                 involves VARCHAR and TIMESTAMP WITH          *
        *                 TIME ZONE columns.                           *
        ****************************************************************
        * PROBLEM DESCRIPTION: An ABEND 04E at DSNIDM.DSNIWKFL:5009    *
        *                      may occur when running a query that     *
        *                      contains an OLAP function and           *
        *                      select list that involves VARCHAR and   *
        *                      TIMESTAMP WITH TIME ZONE columns.       *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An ABEND04E can occur at location DSNIDM.DSNIWKFL:5009 when
        running a query that contains an OLAP function and
        select list that involves VARCHAR and TIMESTAMP WITH TIME
        ZONE columns.

        A sample query that may cause this abend is shown as follows:

        SELECT
1              VH10NN
              ,MIN(VH10NN)    OVER (PARTITION BY CH2NN
                                    ORDER BY     INTIDNN DESC
                                    RANGE BETWEEN UNBOUNDED PRECEDING
                                              AND CURRENT ROW
                                    ) AS MINVH10
              ,TSTZ
              ,MAX(TSTZ)      OVER ()
              ,ROW_NUMBER ()  OVER (PARTITION BY INT1NN
                                    ORDER BY     INTIDNN
                                   )
        FROM  TB015E0
        WHERE INT1NN IN (3,5)
          AND DEC10_2NN >= 33
          AND SINT BETWEEN -5  AND 5
        ORDER BY
                 INT1NN
                ,DEC10_2NN
                ,INTIDNN
        ;
        The code in DB2 is modified to process the TIMESTAMP WITH TIME
        ZONE properly which will prevent the abend.

        Additional Keywords: SQLOLAP SQLRANK SQLDENSERANK
                             SQLROWNUMBER SQLTIMESTAMPTZ
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM92612
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        See PM92612 APAR/PTF text in the PTF cover letter for
        additional information about why a REBIND is necessary.

        Apar PM92612 corrects a problem that can cause an ABEND04E
        at DSNIDM.DSNIWKFL:5009 when running a query that contains
        an OLAP function and select list that involves
        VARCHAR and TIMESTAMP WITH TIME ZONE columns.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        See PM72976 APAR/PTF text in the PTF cover letter for
        additional information about why a REBIND is necessary.

        Apar PM72976 corrects a problem that can cause an ABEND04E
        RC00C90101 at DSNIDM.DSNONLLE:5003 when running a query that
        contains an OLAP function and a group by clause that references
        a LOB column.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
1   COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOWIN  PM92612

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM92612   DSNXOWIN

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOWIN

      LISTEND
 UK96107 COVER LETTER END


 UK96120 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM92712 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS users                       *
        ****************************************************************
        * PROBLEM DESCRIPTION: RC00C90101 DSNKIXDB ERQUAL5002 during   *
        *                      DB2 restart after a system point in     *
        *                      time RESTORE utility which involves a   *
        *                      compressed index.                       *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        In system point in time RESTORE processing, DSM extend module
        may be called to preformat an empty data set of a compressed
        index, followed by a BM close and (re)open.  For BM open call,
        the compressed index flag is not passed properly at the piece
        level to BM.  BM processes the pages as non-compressed with
        wrong page size.  As a result, DB2 restart after RESTORE may
        abend DSNKIXDB erqual5002 when accessing the index directory
        page but is given a wrong page.
        DSM extend module is fixed to pass the compressed index flag at
        the piece level to BM open.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM92712
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNPXTN0  PM92712

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM92712   DSNPXTN0

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNPXTN0

1     LISTEND
 UK96120 COVER LETTER END


 UK96122 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM91151 -
        ****************************************************************
        * USERS AFFECTED: ALL DB2 10 for z/OS users of REBUILD INDEX   *
        *                 rebuilding indexes on database DSNDB01.      *
        ****************************************************************
        * PROBLEM DESCRIPTION: DSNT501I and DSNT376I timeout           *
        *                      during REBUILD INDEX SHRLEVEL           *
        *                      CHANGE of DSNDB01X or DSNDB1XA.         *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        REBUILD INDEX SHRLEVEL CHANGE of index SYSIBM.DSNDB01X
        and SYSIBM.DSNDB1XA take a long time.  While building
        the index when the underlying data set does not exist,
        the elapsed time taken to complete the utility takes
        thirty minutes to build an index with only 38 entries.

        During the execution of the utility, MSGDSNT376I with
        CORRELATION-ID REBUILD CONNECTION-ID UTILITY and
        MSGDSNT501I RC00C900BA are issued on the console.  The
        subtask within REBUILD to build the index is getting a
        timeout on the REBUILD INDEX main task.
        The code has been changed to recognize directory index
        spaces DSNDB01.DSNDB01X and DSNDB01.DSNDB1XA. They will now
        be processed by the REBUILD logic containing special handling
        for directory objects.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM91151
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUGUTC  PM91151

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM91151   DSNUGUTC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUGUTC

      LISTEND
 UK96122 COVER LETTER END


 UK96141 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89307 -
1       ****************************************************************
        * USERS AFFECTED: All DB2 users in a data sharing environment  *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C90101 in DSNIBHRE         *
        *                      ERQUAL5005                              *
        *                                                              *
        *                      MSGDSNB212I, MSGDSNB215I, MSGDSNI014I   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The group buffer pool (GBP) checkpoint process does not properly
        serialize with BACKUP SYSTEM utility. When BACKUP SYSTEM utility
        is run and a GBP checkpoint is taken during the system level
        backup (SLB) process, DB2 continues to castout pages that may
        not be copied to the SLB. When the SLB is used as a base to
        clone a DB2 subsystem, and the cloned system is conditionally
        restarted using this GBP checkpoint, restart abended during a
        GRECP recovery as this GBP checkpoint was incorrectly taken
        during the SLB process and it does not cover all the missing
        updates.
        The GBP checkpoint operation has been fixed to serialize with
        the BACKUP SYSTEM utility by acquiring a PITR Lock. This will
        prevent a GBP checkpoint from being taken while the SLB is in
        progress.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89307
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNB1DLK  PM89307
       DSNB5SCO  PM89307

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89307   DSNB1DLK DSNB5SCO

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNB1DLK
       DSNB5SCO

      LISTEND
 UK96141 COVER LETTER END


 UK96165 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM91545 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 for zOS.                    *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C4 or ABEND0C1 on a branch from   *
        *                      ENF exit module IEFENFSR during DB2     *
        *                      termination.                            *
1       ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        During DB2 termination (normal or abnormal), an ABEND0C4 or
        ABEND0C1 could occur on a branch from ENF exit module IEFENFSR
        if the exit is driven after DB2 has deleted E/CSA load
        modules.
        DB2 has been changed to delete the ENF exit registration
        before the E/CSA load modules are deleted during DB2
        termination.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM91545
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNSCTL   PM91545
       DSN3SSI1  PM91545

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM91545   DSNSCTL  DSN3SSI1

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNSCTL
       DSN3SSI1

      LISTEND
 UK96165 COVER LETTER END


 UK96169 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM77280 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS users of BACKUP SYSTEM and  *
        *                 RESTORE SYSTEM in environments that perform  *
        *                 ALTER TABLE ADD PARTITION                    *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNIDBPL ERQUAL50CC *
        *                      or                                      *
        *                      ABEND04E RC00C90101 DSNIDBAB ERQUAL500A *
        *                      during RESTORE SYSTEM when the activity *
        *                      being log-applied includes ALTER TABLE  *
        *                      ADD PARTITION                           *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The aforementioned abends during RESTORE SYSTEM indicate that
        the caller of DBET is trying to turn on an exception state on a
        partition that is higher than what DBET's internal structure is
        aware of. For example, the caller is trying to turn on RBDP on
        index partition 4 but DBET's structure shows that the index only
        has 3 partitions.
1
        Investigation showed that during mainline when the ALTER TABLE
        ADD PARTITION statement was executed, DBET had no update to do
        because the object of interest had no pending or restrictive
        states at the time (no entry in DBET).

        Then during RESTORE SYSTEM, the object was added to DBET with X
        number of partitions, as result of RESTORE SYSTEM's function,
        not as result of applying a log record. Then RESTORE SYSTEM
        proceeded through the ALTER TABLE ADD PARTITION portion of the
        log apply, however this by design did not invoke DBET to update
        the number of partitions, given that in the mainline when the
        ALTER TABLE ADD PARTITION statement took place, DBET had no
        exception states for the object and hence no log record for the
        ALTER.

        So now in RESTORE SYSTEM when DBET was subsequently called to
        turn on an exception state for partition X+1, DBET abended given
        that it was out of synch with other DB2 components regarding the
        number of partitions.
        DB2 has been modified to write a diagnostic log record when
        ALTER TABLE ADD PARTITION is executed, which will be written if
        the object does not have any exception states - meaning if the
        object is not in DBET.

        During RESTORE SYSTEM, this log record will be applied so that
        the the DBET structure is up to date with regard to the current
        number of partitions for the object.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM77280
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNGDADP  PM77280
       DSNGDAPT  PM77280
       DSNIDBAB  PM77280
       DSNIDBLG  PM77280
       DSNIIEPL  PM77280

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM77280   DSNGDADP DSNGDAPT DSNIDBAB DSNIDBLG DSNIIEPL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNGDADP
       DSNGDAPT
       DSNIDBAB
       DSNIDBLG
       DSNIIEPL

      LISTEND
 UK96169 COVER LETTER END

1
 UK96177 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89292 -
        ****************************************************************
        * USERS AFFECTED: DB2 users.                                   *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C200D8 in DSNB1CPP, when   *
        *                      closing a multi-piece non-partitioned   *
        *                      table space or index.                   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The pageset physical close function has logic to clean up some
        control blocks in the event that they have become corrupted due
        to storage overlays or cancel windows.  For a non-partitioned
        object with multiple datasets, this cleanup may leave an invalid
        count in the control block for a dataset other than the first
        one.  This bad count may result in an ABEND04E RC00C200D8 in
        DSNB1CPP, which brings down DB2.
        The physical close cleanup logic has been modified to ensure
        that the control blocks for the second or subsequent dataset
        of a non-partitioned pageset is properly cleaned up.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89292
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNB1CFC  PM89292
       DSNB1CPP  PM89292

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89292   DSNB1CFC DSNB1CPP

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNB1CFC
       DSNB1CPP

      LISTEND
 UK96177 COVER LETTER END


 UK96186 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM82908 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of SQL             *
        *                 table functions.                             *
        ****************************************************************
        * PROBLEM DESCRIPTION: SQL table functions that contains       *
        *                      range and between predicates that       *
        *                      reference to an SQL table function      *
1       *                      parameter may resulted in a stage       *
        *                      2 predicate.                            *
        *                      After this PTF, all the predicates      *
        *                      in the SQL table functions that         *
        *                      satisfy the following conditions        *
        *                      will be stage 1 predicate.              *
        *                      1. The predicate is a range or          *
        *                      BETWEEN.                                *
        *                      2. The predicate is non boolean         *
        *                      term predicate.                         *
        *                      3. For the range predicate, the         *
        *                      left hand side must be a column         *
        *                      and the right hand side must be         *
        *                      an SQL table function parameter.        *
        *                      The left hand side and right            *
        *                      hand side operands must have            *
        *                      the same type, length and               *
        *                      CCSID.                                  *
        *                      4. For the BETWEEN predicate, the       *
        *                      mid operand must be a column            *
        *                      and the low bound and high bound        *
        *                      must be SQL table function              *
        *                      parameters. The mid, low and            *
        *                      high bounds must have the same type,    *
        *                      length and CCSID.                       *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        SQL table functions that contains range and between predicates
        that reference to an SQL table function parameter may resulted
        in a stage 2 predicate.

        For Example,
          CREATE TABLE T1 (C1 INT);

          CREATE FUNCTION TUDF1(P1 INT)
           RETURNS TABLE(C1 INT)
           RETURN
            SELECT C1 FROM TEST1 WHERE C1 = P1;

        DB2 will process predicate C1 = P1 as stage 1 predicate.
        DB2 was modified to evaluate predicates in the SQL table
        functions that satisfy the restrictions as stage 1.

        Additional KeyWords: SQLTABLEUDF SQLSTAGE1 SQLSTAGE2
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM82908
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:

        See PM83987 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM83987 corrects a problem of non-optimal access path may be
1       selected when an SQL statement satisfies all of the following
        conditions:
        1. EXISTS predicate is used in WHEN clause of CASE expression;
        2. multiple tables are referenced in FROM 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.
      DB2BIND:
        ***Action for PM82908:

        See PM82908 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM82908 corrects a problem of non optimal performance may occur
        for an SQL statement that references to an SQL table function
        that contains a range or between predicate that references to an
        SQL table function parameter. Such predicate may result in a
        stage 2 predicate.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM81762:

        See PM81762 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM81762 corrects a problem that ABEND04E RC00E72088 at the
        location DSNXGRDS DSNXSINE OFFSET3196 could happen for an INSERT
        with SELECT statement that contains ORDER BY and a LOB column in
        the SELECT list.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOBM   PM82908
       DSNXOB2   PM82908
       DSNXOEXC  PM82908
       DSNXOGA   PM82908
       DSNXOMB   PM82908
       DSNXOMIS  PM82908
       DSNXOOS2  PM82908
       DSNXOVC   PM82908
       DSNXOVP   PM82908
       DSNXOW2C  PM82908
       DSNXOW2D  PM82908
       DSNXO1S   PM82908

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1      PM82908   DSNXOBM  DSNXOB2  DSNXOEXC DSNXOGA  DSNXOMB  DSNXOMIS
                 DSNXOOS2 DSNXOVC  DSNXOVP  DSNXOW2C DSNXOW2D DSNXO1S

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOBM
       DSNXOB2
       DSNXOEXC
       DSNXOGA
       DSNXOMB
       DSNXOMIS
       DSNXOOS2
       DSNXOVC
       DSNXOVP
       DSNXOW2C
       DSNXOW2D
       DSNXO1S

      LISTEND
 UK96186 COVER LETTER END


 UK96187 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90189 -
        ****************************************************************
        * USERS AFFECTED: DB2 for z/OS V10 NFM users of XML in         *
        *                 multi-versioning format                      *
        ****************************************************************
        * PROBLEM DESCRIPTION: Following symtoms are possible:         *
        *                      1. SQLCODE904 RC00C90096 during select  *
        *                      to multi-versioning XML using ISO-UR    *
        *                      (UNCOMMITTED READ).                     *
        *                      2. LOCK ESCLATION to XML table space    *
        *                      by select to multi-versioning XML using *
        *                      ISO-UR                                  *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        SQLCODE904 with RC00C90096 and TYPE OF RESOURCE 00000F81 or lock
        escalation occur on select of XML even though the XML is in new
        multi-versioning format and the isolation level is UR. The
        reason is that DB2 accumulated auto-released XML locks, and
        caused NUMLKUS or NUMLKTS to be exceeded.
        DB2 Code has been modified to avoid accumulating the
        XML locks if they are auto-release ones.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM90189
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNIACCH  PM90189
       DSNIADR   PM90189
1      DSNIONXP  PM90189
       DSNIRNXT  PM90189
       DSNIRPRE  PM90189
       DSNIRPRV  PM90189
       DSNIRSET  PM90189
       DSNISRID  PM90189

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90189   DSNIACCH DSNIADR  DSNIONXP DSNIRNXT DSNIRPRE DSNIRPRV
                 DSNIRSET DSNISRID

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIACCH
       DSNIADR
       DSNIONXP
       DSNIRNXT
       DSNIRPRE
       DSNIRPRV
       DSNIRSET
       DSNISRID

      LISTEND
 UK96187 COVER LETTER END


 UK96188 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90902 -
        ****************************************************************
        * USERS AFFECTED: DB2 9 for z/OS and DB2 10 for z/OS users of  *
        *                 parallelism with query containing the same   *
        *                 scalar function in both selection list and   *
        *                 ORDER BY clause.                             *
        ****************************************************************
        * PROBLEM DESCRIPTION: A SQLCODE -180 issued by DSNXRTIM may   *
        *                      occur when a query contains the same    *
        *                      scalar function in both selection       *
        *                      list and ORDER BY clause running on     *
        *                      parallel.                               *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        A SQLCODE -180 issued by DSNXRTIM may occur when a query
        contains the same scalar function in both selection list and
        ORDER BY clause. It is because the sharable buffer is not
        align correctly when running on parallel.

        Following is an example of failing query:

        SELECT VARCHAR(X.C1) AS DATE1, VARCHAR(X.DATEX) AS DATE2,
               VARCHAR(X.CHAR1, 1) AS MYCHAR
          FROM (SELECT B.C2, B.C3, B.C4, B.C1, A.C5 AS DATEX,
                       'I' AS CHAR1
                  FROM T1 A , T2 B ) AS X,
1              T3 Z
         WHERE    X.C2 = 0
           AND    X.C3 = 9643000
           AND    X.C4 = Z.C4
         ORDER    BY DATE(DATE1) DESC, DATE(DATE2) DESC ;

        Note: DATE1 and DATE2 are the scalar function result in the
              selection list which also be referenced in the ORDER BY
              clause
        DB2 is modified to align the parallel buffer correctly when the
        same scalar function appears in both selection list and ORDER
        BY clause.

        Additional Keywords: SQLORDERBY PARALLELISM SQLPARALLELISM
                   DB2PARALL/K SQLVARCHAR SQLCODE180
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM90902
    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.

        To make this fix effective for a static application, it must 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.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOGRL  PM90902

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90902   DSNXOGRL

1     THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOGRL

      LISTEND
 UK96188 COVER LETTER END


 UK96195 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM92508 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for           *
        *                 z/OS users of REPORT TABLESPACESET utility   *
        *                 on directory objects.                        *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00E40900 DSNUGMSG +x'149E'   *
        *                      and MSGDSNU299I occurred when REPORT    *
        *                      TABLESPACESET ran on directory objects  *
        *                      (table spaces in database DSNDB01).     *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available.         *
        ****************************************************************
        REPORT TABLESPACESET on directory objects got ABEND04E
        RC00E40900 at DSNUGMSG OFFSET149E because the table name
        of the directory objects couldn't be obtained from the DB2
        catalog which caused an abend in later CCSID conversion for
        the table name.
        REPORT TABLESPACESET utility code was modified to report
        tablespaceset information for all directory objects correctly.
        MSGDSNU588I - 'NO DATA TO BE REPORTED'
        will no longer be issued for REPORT TABLESPACESET on
        DSNDB01.DBD01, DSNDB01.SYSDBDXA, DSNDB01.SPT01, DSNDB01.SCT02
        and DSNDB01.SYSLGRNX.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM92508
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUGTBN  PM92508
       DSNUPSET  PM92508
       DSNUPTSS  PM92508

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM92508   DSNUGTBN DSNUPSET DSNUPTSS

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUGTBN
       DSNUPSET
       DSNUPTSS

1     LISTEND
 UK96195 COVER LETTER END


 UK96203 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM75495 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS       *
        *                 users of REORG utility against table space   *
        *                 containing XML columns.                      *
        ****************************************************************
        * PROBLEM DESCRIPTION: REORG TABLESPACE containing XML         *
        *                      columns encountered an ABEND0C4         *
        *                      RC0000003 at DSNXESES OFFSET0504        *
        *                      during UNLOAD phase.                    *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        REORG TABLESPACE containing XML columns encountered an ABEND0C4
        RC00000038 at DSNXESES OFFSET0504 during UNLOAD phase when
        extracting the clustering index key, the XML node id index is
        treated as an index on expression improperly.
        DB2 code has been modified to use correct way to extract XML
        node ID index keys during UNLOAD phase of REORG.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM75495
    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  PM75495
       DSNISTRI  PM75495
       DSNUCRUL  PM75495
       DSNUKIUL  PM75495
       DSNURFBR  PM75495
       DSNURSCN  PM75495
       DSNUSTBL  PM75495
       DSNUULXA  PM75495

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM75495   DSNIRFNX DSNISTRI DSNUCRUL DSNUKIUL DSNURFBR DSNURSCN
                 DSNUSTBL DSNUULXA

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIRFNX
       DSNISTRI
       DSNUCRUL
       DSNUKIUL
       DSNURFBR
       DSNURSCN
       DSNUSTBL
       DSNUULXA
1
      LISTEND
 UK96203 COVER LETTER END


 UK96212 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM87039 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users who use  *
        *                 LOB type SQL variables in a native SQL       *
        *                 procedure or non-inline SQL scalar function. *
        ****************************************************************
        * PROBLEM DESCRIPTION: SQLCODE904 RC00C900D1 may occur when an *
        *                      SQL variable of LOB type is used in a   *
        *                      native SQL procedure or non-inline SQL  *
        *                      scalar function and there is CCSID      *
        *                      conversion needed to process the SQL    *
        *                      statement where the LOB SQL variable    *
        *                      is referenced.                          *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Here is an example to show the failing case.

         =========
          EXAMPLE
         =========

         CREATE PROCEDURE MYPROC
         BEGIN

          DECLARE sSQL CLOB(1G) CCSID ASCII;
          DECLARE xSQL DBCLOB(1G) CCSID EBCDIC;
          DECLARE sINT INT;

          SET sSQL = sSQL || xSQL;
          SET sSQL = sSQL || xSQL;
          SET sSQL = sSQL || xSQL;
          ...

         END

        In the above example, each SET statement concatenates xSQL to
        the end of sSQL. When MYPROC contains a large number of these
        SET statements, SQLCODE904 may occur to indicate that there is
        an unavailable resource during execution.

        DB2 code has been modified to handle the aforementioned problem
        correctly.

        Additional keywords: SQLNATIVESQLPL SQLCCSID SQLLOB SQLCODE904

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM87039
    SPECIAL CONDITIONS:
1     COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM79005:

        See PM79005 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM79005 corrects a problem that incorrect output could happen
        for a MERGE SQL statement with a parameter marker that exists in
        the USING clause and compares with a constant in a predicate or
        in a search condition of a CASE expression.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM71068:

        See PM71068 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM71068 corrects a problem of ABEND04E RC00C90101 DSNIBNRF 5003
        or ERQUAL5003 that may occur for an SQL statement that satisfies
        the following conditions:
        1. The SQL statement references to a recursive common table
        expression.
        2. The common table expression contains a UNION ALL and
        outer join.
        3. The select list of the one branch of the UNION ALL
        references to a not null column which came from the
        preserving side table of the outer join. The select list
        of the other branch references to a not null value.
        4. The values on both select list have different types or 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 PM69519:

        See PM69519 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM69519 corrects a problem that ABEND04E RC00E70005 at the
        location DSNXGRDS.DSNXORLI:M111 may happen for an SQL statement
        that ORDER BY any empty string constant and parallelism is
        enabled.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
1       ***Action for PM59659:

        See PM59659 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM59659 corrects a problem of ABEND04E RC00C90101 at
        DSNXIDM .DSNXOTFLA:5009 (in DB2 10) , ABEND04E RC00C900D0 at
        DSNXGRDS.DSNXROHB+9FF6(in DB2 10) or unexpected SQLCODE -404
        (in DB2 9) could occur when a SQL statement references a LOB
        datatype and a different CCSID non LOB datatype in an 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.
      ACTION:
        PM87039 corrects a problem where SQLCODE904 RC00C900D1 may
        occur when an SQL variable of LOB type is used in a native
        SQL procedure or non-inline SQL scalar function and there
        is CCSID conversion needed to process the SQL statement
        where the LOB SQL variable is referenced.

        After the application of this PTF, ALTER PROCEDURE REGENERATE is
        required for each native SQL procedure that is affected, or
        ALTER FUNCTION REGENERATE is required for each non-inline SQL
        scalar function that is affected. Review the PTF cover
        letter to determine which, if any, native SQL procedure or
        non-inline SQL scalar function could be affected by this change.
      ACTION:
        This PTF fixes the problem of incorrect information
        could be recorded in the catalog SYSCOLUMNS for an
        ALTER statement that satisfies the following conditions:
        1. The ALTER statement is used to modify the
        data type of the base table columns.
        2. This base table column is used inside a view
        that contains UNION / UNION ALL.
        To make this fix effective, the view that satisfies
        the conditions above must be drop and recreate or
        regenerate with the ALTER VIEW REGENERATE statement.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOCAS  PM87039
       DSNXOCF   PM87039
       DSNXOCT   PM87039
       DSNXODTR  PM87039
       DSNXOFD   PM87039
       DSNXOFN2  PM87039
       DSNXOFN3  PM87039
       DSNXOFP   PM87039
       DSNXONDA  PM87039
       DSNXORCM  PM87039
       DSNXOSTP  PM87039
       DSNXOTCO  PM87039
       DSNXOTCP  PM87039
       DSNXOTDA  PM87039
       DSNXOW1   PM87039
1
      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM87039   DSNXOCAS DSNXOCF  DSNXOCT  DSNXODTR DSNXOFD  DSNXOFN2
                 DSNXOFN3 DSNXOFP  DSNXONDA DSNXORCM DSNXOSTP DSNXOTCO
                 DSNXOTCP DSNXOTDA DSNXOW1

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOCAS
       DSNXOCF
       DSNXOCT
       DSNXODTR
       DSNXOFD
       DSNXOFN2
       DSNXOFN3
       DSNXOFP
       DSNXONDA
       DSNXORCM
       DSNXOSTP
       DSNXOTCO
       DSNXOTCP
       DSNXOTDA
       DSNXOW1

      LISTEND
 UK96212 COVER LETTER END


 UK96217 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89605 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 10 for z/OS who have        *
        *                 queries using IS NULL on a column which has  *
        *                 histogram statistics collected on it, and    *
        *                 there is only a single quantile              *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0CC RC0C in DSNXOCCX +10F74        *
        *                      ( may appear as DSNXOCCX +0F74 )        *
        *                      or poor query performance               *
        *                      can occur for a query matching the      *
        *                      criteria specified in the Users         *
        *                      Affected section                        *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        ABEND0CC RC0C in DSNXOCCX +10F74 or poor query performance
        can occur for a query that uses IS NULL on a column with
        histogram statistics collected on it and there is only a
        single quantile.  Also, the single quantile represents the
        NULL frequency.

        An internal filter factor calculation can pick up a garbage
        value for the filter factor when checking for a null frequency
        on an IS NULL predicate and a single histogram quantile exists
1       for the column.

        Additional Keywords:
        HISTOGRAM OFFSET0F74 OFFSET10F74 OFFSET010F74
        SQLISNULL INDEXPROBING FILTERFACTOR SQLACCESSPATH SQLPERFORMANCE
        Code is added to prevent picking up a garbage value for the
        filter factor.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89605
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        A rebind is necessary for static applications to rebuild
        access paths based on changes in this APAR.

        PM89605 corrects a problem where ABEND0CC RC0C in DSNXOCCX+0F74
        or poor query performance could occur for a query with an
        IS NULL on a column with histogram statistics collected on it
        and there is only a single quantile.  Also, the single quantile
        represents the NULL frequency.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM89036:

        See PM89036 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM89036 corrects a problem of SQL performance for a user
        whose queries contain join predicates with histogram
        statistics on both of the join columns.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM80699:

        A rebind is necessary to rebuild package and/or plan structures
        based on the changes in this APAR.

        PM80699 corrects a problem that incorrect output may be
        returned for a query with a GROUP BY list which has a SUBSTR or
        YEAR function as well as the column referenced by the function.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM78070:
1
        See PM78070 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM78070 corrects a problem of incorrect output that can happen
        for a query which contains UNION, EXCEPT, EXCEPT ALL or
        ORDER BY and whose top query block has exactly one table.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM75364:

        See PM75364 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM75364 corrects a problem of inaccurate filter factor estimate
        of an IS NOT DISTINCT FROM predicate that may result in an
        inefficient access path.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM74991:

        See PM74991 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM74991 corrects a problem of choosing a poorly performing
        access path for queries containing predicates on columns
        where frequency or histogram statistics have been collected.
        The predicate is a range predicate with parameter marker (or
        parameter markers) or host variable (or host variables), or
        the predicate refers to a subquery (except an EQUAL or
        NOT EQUAL subquery).

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXODFB  PM89605
       DSNXODFE  PM89605
       DSNXODFR  PM89605
       DSNXODFT  PM89605
       DSNXOINQ  PM89605
       DSNXOPRP  PM89605

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89605   DSNXODFB DSNXODFE DSNXODFR DSNXODFT DSNXOINQ DSNXOPRP

1     THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXODFB
       DSNXODFE
       DSNXODFR
       DSNXODFT
       DSNXOINQ
       DSNXOPRP

      LISTEND
 UK96217 COVER LETTER END


 UK96219 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM85936 -
        ****************************************************************
        * USERS AFFECTED: Users of DB2 for z/OS who use DSNADMSB       *
        *                 and/or the stored procedure                  *
        *                 ADMIN_INFO_SQL who have PM73555 applied      *
        *                 (UK83945 for V10; UK83946 for V9)            *
        ****************************************************************
        * PROBLEM DESCRIPTION: THIS FIX ADDRESSES SEVERAL ISSUES       *
        *                      RELATED TO OUTPUT FROM ADMIN_INFO_SQL   *
        *                      FOR DDL AND STATISTICS. THE SYMPTOMS    *
        *                      USUALLY ARE INCORRECT OUTPUT WHEN       *
        *                      BUILDING THE DDL AND STATS OUTPUT       *
        *                      FILES OR CAN RELATE TO LONG             *
        *                      PROCESSING TIME.                        *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        ADMIN_INFO_SQL was sometimes not producing the
        correct output when creating DDL and STATS output files to
        be used for DB2 problem analysis.

        Here is a list of reported issues:

          - Ignore DB errors from Accelerator tables
          - Check ZPARM ACCEL for Accelerator existence
          - Bad input parameter message now in the log
          - Zero out error msg_var when DSNADMMW is called
          - PLAN_TABLE APPLNAME column from 9 to 24 bytes
          - Business time check constraint display problem
          - Remove duplicate call to SYSTABLES to get Clone/Base
            relationship
          - SQLCODE514 problems for V10 CM8

        ADMIN_INFO_SQL has several new features added:

          - Allow Test for input parameters
          - Collect DSN_FILTER_TABLE collection
          - Collect PACKAGE information from BIND collection
          - Collect Synonym info for Views
          - Added check for alias PLAN_TABLE input
1         - Recoded ZPARM collection for speed
          - Collect QUERYINFO table only when accelerator is on

        The reported ADMIN_INFO_SQL problems are now corrected.

        ADDITIONAL KEYWORDS:
        SQLSP SQLSTOREDPROC ADMININFOSQL

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM85936
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        This PTF modifies DSNADMSS, the external module for
        SYSPROC.ADMIN_INFO_SQL, a DB2-supplied routine that can be used
        to collect DB2 environmental service data.  These instructions
        supersede any previous PTF instructions.

        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 modules DSNADMSB and DSNADMSS
            plus the DBRM for DSNADMSS (the DBRM for DSNADMSB is not
            updated).  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.

        ---------------------------------------------------------------
        (2) Refresh the WLM environment
        ---------------------------------------------------------------
        ==> All DB2 V10 customers who use the SYSPROC.ADMIN_INFO_SQL
            stored procedure need to take this action after applying
            the PTF.

            Issue the following VARY MVS command from the console to
            refresh the WLM application environment:
1
              VARY WLM,APPLENV=!wlmenv!,REFRESH

            where !wlmenv! is the name of the WLM application
            environment for running the SYSPROC.ADMIN_INFO_SQL stored
            procedure.

        ---------------------------------------------------------------
        (3) Update your customized copy of job DSNTEJ6I
        ---------------------------------------------------------------
        ==> All DB2 V10 customers who maintain a customized copy of
            DSNTEJ6I need to take this action after applying the PTF.

            The change affects the default input for the following
            parameters:

            Change COLLECT_COLUMN_STATS  to N
            Change EDIT_DDL              to Y

            These default changes are made to minimize the amount of
            data that is collected.  Column statistics can be abundant,
            but are not always required for analysis.  Edit mode will
            help create DDL in a format that can be more easily applied
            to a service environment.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSN@DMSB  PM85936
       DSN@DMSS  PM85936
       DSNADMSB  PM85936
       DSNADMSS  PM85936
       HDBAA10J  PM85936

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM85936   DSN@DMSB DSN@DMSS DSNADMSB DSNADMSS HDBAA10J

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNADMSB
       DSNADMSS

      MACROS
       DSN@DMSB
       DSN@DMSS

      LISTEND
 UK96219 COVER LETTER END


 UK96222 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM92589 -
        ****************************************************************
        * USERS AFFECTED: Users of external SQL procedures or          *
        *                 applications with an SQL statement           *
        *                 that contains a long literal string greater  *
1       *                 than 255 bytes on DB2 for z/OS Version 9,    *
        *                 10 and 11.                                   *
        ****************************************************************
        * PROBLEM DESCRIPTION: An ABEND0C4 may occur when a long       *
        *                      literal string with a length greater    *
        *                      than 255 bytes is used in an SQL        *
        *                      statement which is either embedded in   *
        *                      an application or in an external SQL    *
        *                      procedure that requires the use of      *
        *                      the DB2 precompiler or                  *
        *                      the DB2 coprocessor.                    *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When using the DB2 coprocessor for an application, or when
        using the DB2 precompiler for an external SQL procedure or an
        application, an ABEND0C4 may occur if an SQL statement contains
        a long literal string greater than 255 bytes.

        Additional keywords: ABEND0C4 DB2PRECOMPILER DB2COPROCESSOR
                             SQLEXTERNALSQLPL
        DB2 code is modified so that the abend no longer occurs.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM92589
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNHTOKR  PM92589

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM92589   DSNHTOKR

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNHTOKR

      LISTEND
 UK96222 COVER LETTER END


 UK96226 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM91873 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 for z/OS who use the XML    *
        *                 aggregate function XMLAGG                    *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C4 RC11 DSNXOTS1 +30D4 when using *
        *                      XMLAGG                                  *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        ABEND0C4 RC11 DSNXOTS1 +30D4 may occur when using XML aggregate
1       function XMLAGG.

        For example:
        SELECT LENGTH(DB_XML_ITEM) AS LEN ,DB_XML_ITEM
        FROM
        ( SELECT TBCREATOR,
          XMLSERIALIZE ( XMLELEMENT( NAME "DB_XML_ITEM",
           XMLFOREST (TBCREATOR, XMLAGG(TAB_XML_ITEM) AS TAB_XML))
           AS CLOB)
          AS DB_XML_ITEM
          FROM
          ( SELECT TBCREATOR, TBNAME, XMLELEMENT (NAME 
"TAB_XML_ITEM",
 
            XMLFOREST (TBNAME, XMLAGG (XMLELEMENT (NAME 
"COL_XML_ITEM",
 
            XMLFOREST (NAME,COLNO,COLTYPE ) ) ) AS COL_XML ) )
            AS TAB_XML_ITEM
            FROM  SYSIBM.SYSCOLUMNS
            WHERE  TBCREATOR = 'SYSIBM'
            GROUP BY   TBCREATOR ,TBNAME ) AS T
          GROUP BY   TBCREATOR  ) AS T2 ;

        A pointer was used incorrectly, leading to the abend.

        Additional Keywords:
        XMLAGG OFFSET30D4
        Code is changed to ensure that the pointer is used appropriately
        to avoid the abend.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM91873
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        A rebind is necessary for static applications to rebuild
        access paths based on changes in this APAR.

        PM81848 corrects a problem of possible incorrect output for a
        query containing ORDER BY, GROUP BY, or set function DISTINCT
        when hybrid join is chosen with SORTN_JOIN=N, an index matches
        the ORDER BY, GROUP BY, or set function DISTINCT columns, and
        no extra sort is added to handle this sorting.

        To make this fix effective for a static application, it must 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
       DSNXOTS1  PM91873

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM91873   DSNXOTS1

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOTS1
1
      LISTEND
 UK96226 COVER LETTER END


 UK96227 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90443 -
        ****************************************************************
        * USERS AFFECTED: All DB2 version 9, 10 and 11 for z/OS users  *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C90101 at DSNIBHUN:500F    *
        *                      occured during online page recovery     *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        During REDO log phase of online page recovery, DB2 didn't turn
        on PGRS1 to protect the hole by applying log of deleting old
        overflow record or shrinking record. There was timing window
        where other UR could occupy space of the hole before the inabort
        UR committed. As a sequence, UNDO log phase of the online page
        recovery might fail with forementioned abend.
        DB2 code is modified to turn on PGRS1 flag during REDO phase of
        online page recovery.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM90443
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNIBHRE  PM90443

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90443   DSNIBHRE

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIBHRE

      LISTEND
 UK96227 COVER LETTER END


 UK96234 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90148 -
        ****************************************************************
        * USERS AFFECTED: All Distributed Data Facility (DDF) users    *
        *                 accessing a stored procedure on DB2 10       *
        *                 for z/OS, where the stored procedure         *
        *                 off-loads a local result set to the          *
        *                 IBM Data Analytics Accelerator (IDAA).       *
        ****************************************************************
        * PROBLEM DESCRIPTION: The following abend symptoms may occur: *
1       *                      1. 04E-00D35011 DSNXGRDS.DSNLZD00:000E  *
        *                      2. 04E-00D35011 DSNLZLLM.DSNLZHP0:0192  *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An application at a remote client calls a stored procedure on
        a DB2 10 for z/OS server where the stored procedure returns a
        result set that has been off-loaded to IDAA.  After the stored
        procedure completes, one of the following independent abend
        symptoms may occur:
        1. 04E-00D35011 DSNXGRDS.DSNLZD00:000E
           The abend occurs when DB2 detects that an unnecessary
           internal operation is being performed.
        2. 04E-00D35011 DSNLZLLM.DSNLZHP0:0192
           The abend occurs because DB2 did not account for all valid
           values to be used in a sanity check performed before
           returning result set data from IDAA.

        DB2 10 for z/OS server processing has been changed to:
        1. avoid performing the unnecessary internal operation.
        2. correct the sanity check to allow for an additional valid
           condition.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM90148
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNLXGVR  PM90148
       DSNLXMRS  PM90148
       DSNLZHP0  PM90148
       DSNXERT2  PM90148

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90148   DSNLXGVR DSNLXMRS DSNLZHP0 DSNXERT2

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNLXGVR
       DSNLXMRS
       DSNLZHP0
       DSNXERT2

      LISTEND
 UK96234 COVER LETTER END


 UK96235 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89499 -
        ****************************************************************
        * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
        *                 Specifically those who have enabled the      *
        *                 new capabilities provided by APAR PM43293    *
1       *                 by utilizing a subsystem parameters (ZPARM)  *
        *                 module with (DSN6FAC) MAXCONQN and/or        *
        *                 MAXCONQW set to a value other than OFF.      *
        ****************************************************************
        * PROBLEM DESCRIPTION: Possible symptoms may include:          *
        *                      - ABEND 0C4-00000004 DSNLCPCR+336       *
        *                      - ABEND 04E-00E2001F DSNSVBK+06E2       *
        *                      - ABEND 04E-00E2000C                    *
        *                        DSNXESR1.DSNSVSVB+0AC2                *
        *                      - ABEND 0C4-00000010 DSNLQCRP+12EE      *
        *                      - ABEND 04E-00E2000C                    *
        *                        DSNLISKM.DSNSVSVB+0AC2                *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        APAR PM43293 provided a new capability to control the amount
        of connection request queuing that can occur at members of
        a data sharing group.  The capability is activated by utilizing
        a subsystem parameters (ZPARMs) module where the values of the
        MAXCONQN and/or MAXCONQW parameters are set to a value other
        than OFF.
        When the connection request queue control capability is
        activated, several possible conditions can occur during the
        process of terminating a client connection:
        - If the client application had requested (hop) access to
          remote location data from the DB2 subsystem, then the (hop)
          connections to the remote locations must also be terminated.
          This leads to abend 0C4-00000004 DSNLCPCR+0336 and a
          subsequent termination of the entire subsystem since the
          abend occurs during "must complete" deallocation 
processing.
 
        - During connection termination processing, DB2 fails to
          free the associated LWEL and LQHD (and hence ROB) control
          blocks.
          A storage leak will occur in the following storage pool(s).
          . DB2 QUEUE ELEMENT POOL
          . DC QUEUE HEADER POOL
          . ROB
          The storage leak may accumulate to the point of causing
          abend 04E-00E2001F.
          Example:
            04E-00E2001F DSNLVCIP.DSNSVBK +0744
        - During connection termination processing, DB2 fails to
          free storage related to any modified session information,
          such as special registers.
          A storage leak will occur in the following storage pool(s).
          . SRGS POOL
          The storage leak may accumulate to the point of causing
          abend 04E-00E2000C.
          Example:
            04E-00E2000C DSNXESRL.DSNSVSVB+0AC2
        - A rare timing condition exists where a connection may undergo
          MAXCONQ* termination processing while the connection
          environment is still in the process of being inactivated
          after just being accepted.
          This may lead to abend 0C4-00000010 DSNLQCRP+12EE.
        - During connection termination processing, DB2 may fail to
1         free communication buffer relate storage.
          A storage leak will occur in the following storage pool(s).
          . DCRM I/O BUFFER POOL
          The storage leak may accumulate to the point of causing
          abend 04E-00E2000C.
          Example:
            04E-00E2000C DSNLISKM.DSNSVSVB+0AC2

        Numerous changes have been made to correct the reported
        conditions.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89499
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNLCBFM  PM89499
       DSNLCPCR  PM89499
       DSNLIENO  PM89499
       DSNLQCRP  PM89499

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89499   DSNLCBFM DSNLCPCR DSNLIENO DSNLQCRP

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNLCBFM
       DSNLCPCR
       DSNLIENO
       DSNLQCRP

      LISTEND
 UK96235 COVER LETTER END


 UK96237 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90355 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS      *
        *                 users of IN-list predicates.                 *
        ****************************************************************
        * PROBLEM DESCRIPTION: An ABEND0C4 RC4 at location DSNXGINL    *
        *                      OFFSET 1CA2 or 1EC0 can occur when an   *
        *                      SQL statement contains 32767 distinct   *
        *                      elements in an IN-list predicate.       *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An ABEND0C4 RC4 can occur at location DSNXGINL OFFSET 1CA2 or
        1EC0 when an SQL statement contains 32767 distinct elements in
        an IN-list predicate.

        An example of a failing query is as follows.
1
          CREATE TABLE T1(C1 INTEGER);

          SELECT * FROM T1 WHERE C1 IN(1, 2, 3, 4, 5, ... ,32767);

        Since there are 32767 distinct values in the IN-list predicate
        for the above SELECT statement, the abend occurs.

        This problem is caused by an internal error when DB2 tries to
        sort the elements of the IN-list predicate.
        DB2 has been modified to process the IN-list predicate properly.

        Additional Keywords: SQLIN OFFSET1CA2 OFFSET1EC0
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM90355
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM89078:

        See PM89078 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM89078 corrects incorrect output for an SQL statement with
        inlist table access and field proc

        To make this fix effective for a static application, it must 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
       DSNXGINL  PM90355

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90355   DSNXGINL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXGINL

      LISTEND
 UK96237 COVER LETTER END


 UK96265 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88528 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of REORG REBALANCE *
        ****************************************************************
        * PROBLEM DESCRIPTION: LIMITKEY in SYSIBM.SYSTABLEPART is      *
        *                      not in the correct external format      *
        *                      after a REORG REBALANCE on a            *
1       *                      partitioned table space when the        *
        *                      limit key is comprised of many columns. *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available.         *
        ****************************************************************
        A REORG REBALANCE utility was executed on a partitioned table
        space.  The partitioning index included more than 50 columns
        of the table.  The REORG REBALANCE was successful, but the
        external representation of the new LIMITKEY inserted into
        SYSTABLEPART was corrupted.  This occurred when the
        concatenated external values of the limit key columns were
        greater than 256 characters and a new work area overwrote
        the existing work area containing the key.
        Code has been modified to correctly concatenate the external
        LIMITKEY inserted into SYSIBM.SYSTABLEPART.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88528
    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  PM88528

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88528   DSNUDALT

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUDALT

      LISTEND
 UK96265 COVER LETTER END


 UK96272 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86485 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of Large Objects   *
1       *                 (LOBs) with the REORG utility.               *
        ****************************************************************
        * PROBLEM DESCRIPTION: An ABEND04E RC00C90101 can occur at     *
        *                      location DSNIDM DSNOGLOB:5062 during a  *
        *                      REORG TABLESPACE SHRLEVEL CHANGE of     *
        *                      a LOB table space in the directory      *
        *                      database, DBD01.                        *
        *                                                              *
        *                      The same error can occur whether the    *
        *                      LOB table space is being reorganized by *
        *                      itself, or as part of the REORG AUX YES *
        *                      operation on the base table space.      *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An ABEND04E RC00C90101 can occur at location DSNIDM DSNOGLOB
        5062 (ERQUAL5062) during a REORG TABLESPACE SHRLEVEL CHANGE of a
        LOB table space in the directory database, DBD01.

        The same error can occur whether the LOB table space is being
        reorganized by itself, or as part of the REORG AUX YES
        operation on the base table space.

        The abend occurs because the expected LOB was deleted and its
        LOB map was reused by another LOB as a data page by DML running
        concurrently with the REORG.

        However, during the REORG LOG apply phase, DB2 REORG attempts to
        locate the deleted LOB when it encounters the insert LOG record
        of the expected LOB.  Since the expected LOB was already deleted
        and committed, there is no need to request a pseudo-deleted
        auxiliary key.
        The code in DB2 is modified to prevent the abend.

        Additional Keywords: SQLLOB
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM86485
    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  PM86485
       DSNOTCSO  PM86485

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM86485   DSNONLLE DSNOTCSO

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNONLLE
       DSNOTCSO

      LISTEND
 UK96272 COVER LETTER END
1

 UK96302 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88321 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS, DB2 10 for z/OS, and     *
        *                 DB2 11 for z/OS utility users.               *
        ****************************************************************
        * PROBLEM DESCRIPTION: Change Data Capture support for         *
        *                      DSNDB01.SYSUTILX prevented a migration  *
        *                      to DB2 for z/OS version 9.              *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available.         *
        ****************************************************************
        Change Data Capture settings interfered with DB2 utilities
        during a migration to DB2 9 for z/OS.

        The DSNTIPO install panel has a DPROP SUPPORT option that can
        be tailored by the end user. DPROP SUPPORT is option 10 in
        DB2 9 for z/OS and option 9 in DB2 for z/OS versions 10 and 11.

        When DPROP SUPPORT was set to a value of 2 it prevented all
        DB2 utilities from running and this prevented the migration to
        DB2 9 for z/OS.

        Another way this problem can happen is if the CHGDC and EDPROP
        ZPARM fields are both set to YES.
        DB2 code has been updated so that DB2 utilities are no longer
        impacted by the values specfied in the DSNTIPO install panel
        field for DPROP SUPPORT and also the CHGDC and EDPROP zparm
        fields.

        Change Data Capture (CDC) was used for directory table space
        DSNDB01.SYSUTILX to ensure complete SYSUTILX records were
        logged during utility operations.

        This APAR disables Change Data Capture for DSNDB01.SYSUTILX
        and thus full logging for SYSUTILX. It also contains code to
        turn full logging back on for SYSUTILX. To re-enable full
        logging for SYSUTILX put the PTFs for this APAR on and then
        take a SHRLEVEL CHANGE or REFERENCE image copy of
        DSNDB01.SYSUTILX. Full logging will be restored for SYSUTILX
        the first time an image copy is taken of it. This only needs
        to be done once, whether you are running in a data sharing
        group or non-data sharing environment.

        It is OK if full logging is not immediately turned back on for
        SYSUTILX. However, DSN1LOGP output for SYSUTILX may appear
        incorrect due to the fact that full log records were not
        available for some amount of time.


        ++HOLD COMMENT FOR RELEASE B10, TYPE ACT:
        ***Action for PM88321:

1       See PM88321 APAR/PTF text for additional information about
        why it is necessary to take an image copy of DSNDB01.SYSUTILX.

        The PTF for APAR PM88321 changes the logging done for
        SYSIBM.SYSUTILX.  Specifically, it disables Change Data
        Capture for DSNDB01.SYSUTILX and re-enables full logging.
        Note that for full logging of SYSUTILX to become effective,
        you must take an image copy of DSNDB01.SYSUTILX.  This only
        needs to be done once, whether you are running in a data
        sharing group or in a non-data sharing environment.

        ++HOLD COMMENT FOR RELEASE A10, TYPE ACT:
        ***Action for PM88321:

        See PM88321 APAR/PTF text for additional information about
        why it is necessary to take an image copy of DSNDB01.SYSUTILX.

        The PTF for APAR PM88321 changes the logging done for
        SYSIBM.SYSUTILX.  Specifically, it disables Change Data
        Capture for DSNDB01.SYSUTILX and re-enables full logging.
        Note that for full logging of SYSUTILX to become effective,
        you must take an image copy of DSNDB01.SYSUTILX.  This only
        needs to be done once, whether you are running in a data
        sharing group or in a non-data sharing environment.

        ++HOLD COMMENT FOR RELEASE 910, TYPE ACT:
        ***Action for PM88321:

        See PM88321 APAR/PTF text for additional information about
        why it is necessary to take an image copy of DSNDB01.SYSUTILX.

        The PTF for APAR PM88321 changes the logging done for
        SYSIBM.SYSUTILX.  Specifically, it disables Change Data
        Capture for DSNDB01.SYSUTILX and re-enables full logging.
        Note that for full logging of SYSUTILX to become effective,
        you must take an image copy of DSNDB01.SYSUTILX.  This only
        needs to be done once, whether you are running in a data
        sharing group or in a non-data sharing environment.

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88321
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        See PM88321 APAR/PTF text for additional information about
        why it is necessary to take an image copy of DSNDB01.SYSUTILX.

        The PTF for APAR PM88321 changes the logging done for
        SYSIBM.SYSUTILX.  Specifically, it disables Change Data
        Capture for DSNDB01.SYSUTILX and re-enables full logging.
        Note that for full logging of SYSUTILX to become effective,
        you must take an image copy of DSNDB01.SYSUTILX.  This only
        needs to be done once, whether you are running in a data
        sharing group or in a non-data sharing environment.
    COMMENTS:
1     CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNGEDB1  PM88321
       DSNUBAFI  PM88321
       DSNUBASA  PM88321
       DSNXIENF  PM88321

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88321   DSNGEDB1 DSNUBAFI DSNUBASA DSNXIENF

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNGEDB1
       DSNUBAFI
       DSNUBASA
       DSNXIENF

      LISTEND
 UK96302 COVER LETTER END


 UK96310 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM85376 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 users running IFI READS with      *
        *                 IFCID 317.                                   *
        ****************************************************************
        * PROBLEM DESCRIPTION: V10 ABEND04E RC00E20018 AT DSNSTKGG     *
        *                      OFFSET 0B64 when IFI READS request was  *
        *                      issued for IFCID 317.                   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        ABEND 04E RC00E20018 AT DSNSTKGG OFFSET 0B64 may happen when
        DB2 processes the IFI READS request for IFCID 317.
        The abend happens because DB2 failed to acquire stack storage to
        convert a very large SQL statement text from UNICODE to EBCDIC
        to insert into the trace records.
        This problem can happen when the requested storage buffer size
        exceeds 512K bytes.
        DB2 code has been modified to allocate storage from GETMAIN
        storage instead of DB2 stack storage when converting very
        large SQL statement text.

        Additional keywords: SQLSTORAGE IFCID317 IFCID318
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM85376
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXECST  PM85376

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1      PM85376   DSNXECST

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXECST

      LISTEND
 UK96310 COVER LETTER END


 UK96313 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM87679 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users who use *
        *                 CASE expression in a BETWEEN predicate       *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C4 RC4 AT DSNXOPRS 8F4C may occur *
        *                      for a query that uses CASE expression   *
        *                      in a non-correlated BETWEEN predicate   *
        *                      and JOIN on multiple tables.            *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
         Here is an example to show the failing case.

          =========
           EXAMPLE
          =========

          CREATE TABLE MYTBA (A1 INT, A2 INT, A3 INT, A4 INT);
          CREATE TABLE MYTBB (B1 INT);
          CREATE TABLE MYTBC (C1 INT);
          CREATE TABLE MYTBD (D1 INT);
          COMMIT;

          SELECT 'TEST'
            FROM MYTBA
                 LEFT OUTER JOIN
                 MYTBB
              ON A1 = B1
                 LEFT OUTER JOIN
                 MYTBC
              ON A1 = C1,
                 MYTBD
           WHERE D1 BETWEEN CASE WHEN A1 = 1
                                 THEN A2
                                 ELSE A3
                               END
                        AND A4;

        DB2 code has been modified to handle the aforementioned problem
        correctly.

        Additional keywords: SQLCASE SQLBETWEEN SQLJOIN SQLNONCORRSUBQ
1
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM87679
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOEXB  PM87679
       DSNXOW2C  PM87679
       DSNXOW2D  PM87679

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM87679   DSNXOEXB DSNXOW2C DSNXOW2D

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOEXB
       DSNXOW2C
       DSNXOW2D

      LISTEND
 UK96313 COVER LETTER END


 UK96317 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM92528 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of OLAP *
        *                 specifications with hybrid join.             *
        ****************************************************************
        * PROBLEM DESCRIPTION: An incorrect result can be returned for *
        *                      a query using an OLAP specification     *
        *                      with hybrid join.                       *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An incorrect result can be returned for a query using an OLAP
        specification with hybrid join.  If an OLAP specification such
        as ROW_NUMBER is used in a query that has an access path with
        hybrid join and the intermediate table overflows, the row number
        result is incorrectly reset to zero which causes the row number
        number values to start over at 1 again.

        The following example illustrates a failing case.

          SELECT ROW_NUMBER() OVER() AS RN
          FROM T1 A, T2 B, T5 C
          WHERE A.C1 = B.C1
          AND   C.C1 = B.C1 ;

        If the intermediate table overflows while processing row number
        5000, the value returned for row 5001 is 1 instead of the
        expected value 5001.
1
        This problem can occur for any OLAP specification and has
        various incorrect results reported dependent on the OLAP spec
        that is used.  The problem can also occur if the rid pool
        overflows (instead of the intermediate table) while processing
        the hybrid join.
        The code in DB2 has been modified to return the correct result.
        The OLAP specification is no longer reset during overflow
        processing.

        Additional Keywords: SQLOLAP SQLHYBRID SQLHYBRIDJOIN
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM92528
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXRCLS  PM92528

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM92528   DSNXRCLS

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXRCLS

      LISTEND
 UK96317 COVER LETTER END


 UK96319 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89698 -
        ****************************************************************
        * USERS AFFECTED: all DB2 9 for z/OS, DB2 10 for z/OS and      *
        *                 DB2 11 for z/OS users of REBUILD INDEX       *
        *                 utility.                                     *
        ****************************************************************
        * PROBLEM DESCRIPTION: An overflow of a DB2 internal           *
        *                      variable causes a sudden drop in the    *
        *                      value of TOTALENTRIES column in         *
        *                      SYSINDEXSPACESTATS when a REBUILD       *
        *                      INDEX utility is run.                   *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        During a REBUILD INDEX utility externalizing Real-time
        statistics (RTS), an internal variable is updated to hold the
        number of index keys reloaded.  An overflow in the field causes
        its value to be truncated, resulting in a sudden drop of the
        TOTALENTRIES column in SYSINDEXSPACESTATS when REBUILD INDEX
        externalizes statistics.
        Additional Keyword: SYSIBM.SYSINDEXSPACESTATS
        DB2 code has been modified to avoid overflow on number of
1       index keys during REBUILD INDEX.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89698
    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  PM89698

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89698   DSNKLOD2

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNKLOD2

      LISTEND
 UK96319 COVER LETTER END


 UK96323 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90157 -
        ****************************************************************
        * USERS AFFECTED: All DB2 V9, 10 or 11 for z/OS users of an    *
        *                 SQL statement that contains a table          *
        *                 expression or view with SET operators, outer *
        *                 joins and multiple CCSIDs.                   *
        ****************************************************************
        * PROBLEM DESCRIPTION: Incorrect output, SQLCODE -404, or      *
        *                      other unexpected behavior due to a      *
        *                      storage overlay could happen 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 null padding-side column of an     *
        *                         outer join exists in the SELECT list *
        *                         of one of the SET operation          *
        *                         branches.                            *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An example is shown below:

        CREATE TABLE T1 ( C1 CHAR(4) NOT NULL, C2 CHAR(4))
          CCSID UNICODE;
        CREATE TABLE T2 ( C1 CHAR(4) NOT NULL, C2 CHAR(4))
          CCSID EBCDIC;
        CREATE TABLE T3 ( C1 CHAR(4) NOT NULL, C2 CHAR(4))
          CCSID EBCDIC;
1       COMMIT;

        INSERT INTO T1 VALUES('C11', 'C21');
        INSERT INTO T1 VALUES('C12', 'C22');
        INSERT INTO T2 VALUES('C11', 'C21');
        INSERT INTO T2 VALUES('C12', 'C22');
        INSERT INTO T3 VALUES('C11', 'C21');
        INSERT INTO T3 VALUES('C12', 'C22');
        COMMIT;

        SELECT TX.C1
        FROM (SELECT T1.C1
              FROM T1
              UNION
              SELECT T3.C1
              FROM T2 LEFT OUTER JOIN T3
                      ON T2.C1 = T3.C1
              ) TX(C1)
        ;

        The query above returns:

          +--------------+
          |      C1      |
          +--------------+
        1_| .C11         |
        2_| .C12         |
        3_| C11          |
        4_| C12          |
          +--------------+

        While the correct result should be:

          +--------------+
          |      C1      |
          +--------------+
        1_| C11          |
        2_| C12          |
          +--------------+

        DB2 did not correctly process the aforementioned SQL statements,
        which caused the incorrect output, SQLCODE -404 or other
        unexpected behavior.
        DB2 has been modified to correctly process the aforementioned
        SQL statement, so there will be no incorrect output, SQLCODE
        -404 or other unexpected behavior.

        Additional keywords: SQLTABLEEXPR SQLUNION SQLUNIONALL
                             SQLINTERSECT SQLINTERSECTALL SQLEXCEPT
                             SQLEXCEPTALL SQLCCSID SQLOUTERJOIN
                             SQLFULLJOIN SQLOUTER SQLFULL SQLJOIN
                             SQLCODE404 DB2OVRLAY/K
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM90157
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
1                LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM90157:

        See PM90157 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM90157 corrects a problem that incorrect output, SQLCODE -404,
        or other unexpected behavior due to a storage overlay could
        happen 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 null padding-side column of an outer join exists 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.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOCT   PM90157
       DSNXONDA  PM90157

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90157   DSNXOCT  DSNXONDA

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOCT
       DSNXONDA

      LISTEND
 UK96323 COVER LETTER END


 UK96335 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM85432 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 z/OS and DB2 10 z/OS users who     *
        *                 specify the KEEPDICTIONARY option during     *
        *                 a REORG with EDITPROCS on the table.         *
        ****************************************************************
        * PROBLEM DESCRIPTION: DB2 was incorrectly writing out         *
        *                      compressed records which had not been   *
        *                      EDITPROC encoded during a REORG when    *
        *                      the KEEPDICTIONARY option was           *
        *                      specified.                              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
1       After PM44787/UK73145/UK73146 or PM65869/UK83961/UK83962 is
        applied and KEEPDICTIONARY is specified during a REORG with
        an EDITPROC on the table, the EDITPROC decoded record could
        be used for compression instead of the EDITPROC encoded
        record.  When this occurs, the compressed EDITPROC decoded
        record is written out to the page. Afterwards, when trying
        to access that record, DB2 decompresses and decodes the
        record, which leads to incorrect results.
        Code has been changed so that if we do have an EDITPROC
        encoded record we will use that to compress the record instead
        of the decoded and decompressed record.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM85432
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        PM85432 does not fix existing data which has been affected
        by this problem, it does prevent future data from becoming
        corrupted by this issue.  The user must identify the objects
        which have been affected and bring the data back to a consistent
        state.  Objects that are affected must have the following
        conditions met:
           - The table must have an EDITPROC.
           - The table space or partition must have COMPRESS YES.
           - REORG with KEEPDICTIONARY must have been run with a
             dictionary present after PM44787/UK73145/UK73146 had been
             applied.

        The following SELECT statement can be used to determine if
        the first two conditions were met:
           SELECT TB.CREATOR, TB.NAME, TB.DBNAME,
                  TB.TSNAME, TP.PARTITION
              FROM SYSIBM.SYSTABLES TB, SYSIBM.SYSTABLEPART TP
              WHERE TB.EDPROC <> ' ' AND
                    TB.DBNAME = TP.DBNAME AND
                    TB.TSNAME = TP.TSNAME AND
                    TP.COMPRESS = 'Y';
        A REPORT RECOVERY can identify the names of the REORG job(s)
        that were run after the PTF was applied, however it cannot
        indicate if the KEEPDICTIONARY keyword was used during the
        REORG at the time.

        Because EDITPROCs can manipulate the data in many different
        ways, below are just a few methods for possibly identifying
        which tables may have corrupted data if it is not possible to
        determine whether or not the above conditions were all met:
         - A table space scan (SELECT * FROM XYZ) can be used to check
           if every record in the table can be EDITPROC decoded and
           displayed in the output, however even if the display is
           successful it is possible the actual output of the data
           is not correct and therefore corrupted.  An ABEND can also
           occur if the data after the EDITPROC decoding cannot be
           properly formatted.
         - If an index is present on the data/column that has been
           EDITPROC encoded then a CHECK INDEX could detect the data
1          corruption with an index/data mismatch if it has not been
           rebuilt after the data was corrupted.  An ABEND can also
           occur if the data after the EDITPROC decoding cannot be
           properly formatted.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNIRLPG  PM85432

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM85432   DSNIRLPG

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIRLPG

      LISTEND
 UK96335 COVER LETTER END


 UK96350 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM92040 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS, DB2 10 for z/OS and      *
        *                 DB2 11 for z/OS users of REORG utility       *
        *                 on partiton-by-growth table spaces.          *
        ****************************************************************
        * PROBLEM DESCRIPTION: MSGDSNU202I - RECOVER PENDING ON TABLE  *
        *                      SPACE PROHIBITS PROCESSING and RC8      *
        *                      from a MODIFY RECOVERY or QUIESCE       *
        *                      utility following a REORG SHRLEVEL NONE *
        *                      on the same partition-by-growth (PBG)   *
        *                      table space with no PBG partitions in   *
        *                      any pending state.                      *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        A REORG TABLESPACE SHRLEVEL NONE on the entire PBG table space
        with MAXPARTITIONS 16 and only 1 active partition ended with
        RC0.  However, a subsequent MODIFY RECOVERY ended with RC8 and
        DSNU202I - RECOVER PENDING ON TABLE SPACE tsname PROHIBITS
        PROCESSING.  A DISPLAY DATABASE showed no restrictive states
        but the DB2 logs revealed that partitions 2 - 16 had been
        placed in RECOVER PENDING (RECP) during the REORG.  The same
        DSNU202I message could occur with other utilities operating
        on objects within the same database as the PBG table space
        which was REORGed.

        REORG was erroneously setting all partitions (MAXPARTITIONS)
        in RECOVER PENDING when partition information could not be
        obtained from the DBD due to concurrent activity on objects
        within the same database, but only the active PBG parts were
        reset at the end of the REORG utility.
        REORG code has been modified to use the number of active
        PBG partitions when setting RECOVER PENDING during REORG.
1   COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM92040
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNURFRP  PM92040

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM92040   DSNURFRP

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNURFRP

      LISTEND
 UK96350 COVER LETTER END


 UK96357 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM31841 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users migrating to       *
        *                 DB2 11 for z/OS.                             *
        ****************************************************************
        * PROBLEM DESCRIPTION: Toleration of fallback from DB2 11      *
        *                      for z/OS.                               *
        *                                                              *
        *                      In a Data Sharing environment,          *
        *                      required for coexistence of             *
        *                      DB2 11 for z/OS with DB2 10 for z/OS.   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        This APAR must be applied to all members of a data sharing
        group and DB2 10 started on all members before one of
        the members can be started with DB2 11 to migrate the
        DB2 catalog. Non-data sharing DB2 subsystems must also run
        with this APAR before attempting to migrate to DB2 11.

        This APAR allows fallback to DB2 10 after a migration to DB2 11
        and also allows release coexistence in a data sharing
        environment.

        Refer to the DB2 11 publications for procedures
        for migration and then subsequent fallback to DB2 10.
        The purpose of this APAR is to allow fallback from DB2 11.
        Refer to the chapters 'Falling back' and 'Remigrating'
        in the DB2 11 Installation Guide for this procedure.

        ++HOLD COMMENT FOR RELEASE A10, TYPE ACT:
        After applying this PTF, you need to re-assemble and linkedit
        DSNHDECP to pick up the changes in DSNARIB. Under DB2 data
1       sharing, if each member of the group has its own DSNHDECP module
        then you need to repeat the steps below for each member.

        These are the steps to update DSNHDECP:
           (1) Create a separate job containing only the DSNTIZP and
           DSNTIZQ steps from the job DSNTIJUZ previously edited
           by the install CLIST.
           (2) Re-assemble and linkedit the DSNHDECP load module
           by running your newly created job to produce a new
           DSNHDECP.
           (3) Stop and start your DB2.

        See INFO APAR II14660 for more information.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM31841
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        After applying this PTF, you need to re-assemble and linkedit
        DSNHDECP to pick up the changes in DSNARIB. Under DB2 data
        sharing, if each member of the group has its own DSNHDECP module
        then you need to repeat the steps below for each member.

        These are the steps to update DSNHDECP:
           (1) Create a separate job containing only the DSNTIZP and
           DSNTIZQ steps from the job DSNTIJUZ previously edited
           by the install CLIST.
           (2) Re-assemble and linkedit the DSNHDECP load module
           by running your newly created job to produce a new
           DSNHDECP.
           (3) Stop and start your DB2.

        See INFO APAR II14660 for more information.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNARIB   PM31841
       DSNGEDLC  PM31841
       DSNIRTSX  PM31841
       DSNRRPRC  PM31841
       DSNRRSBS  PM31841
       DSNTSTR2  PM31841
       DSNUECM2  PM31841
       DSNUEXDB  PM31841
       DSNUGMAP  PM31841
       DSNXCATL  PM31841
       DSNXCOBC  PM31841
       DSNXKFUN  PM31841
       DSNXLDBD  PM31841
       DSN7GCMD  PM31841

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM31841   DSNARIB  DSNGEDLC DSNIRTSX DSNRRPRC DSNRRSBS DSNTSTR2
                 DSNUECM2 DSNUEXDB DSNUGMAP DSNXCATL DSNXCOBC DSNXKFUN
                 DSNXLDBD DSN7GCMD

1     THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNARIB
       DSNGEDLC
       DSNIRTSX
       DSNRRPRC
       DSNRRSBS
       DSNTSTR2
       DSNUECM2
       DSNUEXDB
       DSNUGMAP
       DSNXCATL
       DSNXCOBC
       DSNXKFUN
       DSNXLDBD
       DSN7GCMD

      LISTEND
 UK96357 COVER LETTER END


 UK96368 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88166 -
        ****************************************************************
        * USERS AFFECTED: This change affects DB2 10 for z/OS          *
        *                 customers who need to run DB2 with more than *
        *                 100000 data sets open concurrently.          *
        ****************************************************************
        * PROBLEM DESCRIPTION: This APAR provides relief for customers *
        *                      who need to run DB2 with more than      *
        *                      100000 concurrently open data sets.     *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available.         *
        ****************************************************************
        The DSMAX subsystem parameter specifies the maximum number of
        data sets that DB2 is allowed to have open at one time.  In DB2
        10, DSMAX currently can be set to any integer from 1 to 100000;
        the default is 20000.  The limit of 100000 is constraining
        certain workloads and needs to be increased.
        In response, this APAR lifts the maximum DSMAX size from 100000
        to 200000 data sets.  The practical limit can be less depending
        on available storage below the 2 GB bar.  Further considerations
        and recommendations:
         * In order to apply this PTF, you must first apply the PTFs for
           APARs PM88165 and PM87969.  These PTFs provide additional
           internal DB2 changes needed to support more than 100000
           concurrently open data sets.

         * Use z/OS Version 1 Release 13 or higher for any DB2 subsystem
           that will have a DSMAX setting greater than 100000.

         * Complete one of the following actions to improve the
           performance of opening and closing data sets:
           - Update the ALLOCxx parmlib member to set the SYSTEM
1            MEMDSENQMGMT value to ENABLE.
           - Issue system command SETALLOC SYSTEM,MEMDSENQMGMT=ENABLE

           Updating the ALLOCxx parmlib is strongly recommended because
           the change remains effective across IPLs. If the SETALLOC
           command is used to enable SYSTEM MEMDSENQMGMT, a DB2 restart
           is required to make the change effective.

         * ATTENTION: A DSMAX setting larger than 100000 will cause a
           noticeable increase in consumption of below-the-bar (BTB)
           storage by z/OS.  Testing by IBM indicates that when the
           number of concurrent data sets opened by DB2 reaches the new
           limit of 200000, z/OS could consume about 700 megabytes of
           storage BTB, consistent with the expected consumption of
           about 4 kilobytes per open data set.  In addition, the DB2
           DBM1 address space can use significant amounts of BTB storage
           when there are many page set objects in DBET exception state.
           Testing by IBM indicates that when there are over 100000
           objects with exception states, mostly ICOPY (33,756) and
           AREO* (67,690), DBET consumes about 400 MB below the bar
           storage.  When below the bar storage constraint occurs, the
           abends RC00E20003, RC00E20013, RC00E20016, or RC00E70005 may
           occur at the next storage request.

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88166
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DOCUMENTATION:

        The DB2 10 Installation Guide is updated to account for
        increasing the maximum value of DSMAX to 200000.  This change
        is now available in the DB2 10 Installation Guide on the IBM
        Information Management website:

         * DSMAX field (DSMAX subsystem parameter) (db2z_ipf_dsmax):
             Change the maximum value to 200000.
         * CLIST calculations panel 1: DSNTIPC (db2z_dsntipc):
             Change the maximum value to 200000 here:
          1  DSMAX - MAXIMUM OPEN DATA SETS    =    20000    (1-100000)
      ACTION:
        ***Action for PM88166 (DB2 10)

        This PTF increases the maximum number of data sets that DB2 is
        capable of having open at one time from 100000 to 200000.  The
        allowed maximum is specified by DB2 parameter DSMAX in DSN6SPRM,
        which can now range from 1 to 200000 data sets.  The DSMAX
        default setting remains 20000.

        Recommendations and considerations:
         * In order to apply this PTF, you must first apply the PTFs for
           APARs PM88165 and PM87969.  These PTFs provide additional
           internal DB2 changes needed to support more than 100000
           concurrently open data sets.

1        * Use z/OS Version 1 Release 13 or higher for any DB2 subsystem
           that will have a DSMAX setting greater than 100000.

         * Complete one of the following actions to improve the
           performance of opening and closing data sets:
           - Update the ALLOCxx parmlib member to set the SYSTEM
             MEMDSENQMGMT value to ENABLE.
           - Issue system command SETALLOC SYSTEM,MEMDSENQMGMT=ENABLE

           Updating the ALLOCxx parmlib is strongly recommended because
           the change remains effective across IPLs. If the SETALLOC
           command is used to enable SYSTEM MEMDSENQMGMT, a DB2 restart
           is required to make the change effective.

         * ATTENTION: A DSMAX setting larger than 100000 will cause a
           noticeable increase in consumption of below-the-bar (BTB)
           storage by z/OS.  Testing by IBM indicates that when the
           number of concurrent data sets opened by DB2 reaches the new
           limit of 200000, z/OS could consume about 700 megabytes of
           storage BTB, consistent with the expected consumption of
           about 4 kilobytes per open data set.  In addition, the DB2
           DBM1 address space can use significant amounts of BTB storage
           when there are many page set objects in DBET exception state.
           Testing by IBM indicates that when there are over 100000
           objects with exception states, mostly ICOPY (33,756) and
           AREO* (67,690), DBET consumes about 400 MB below the bar
           storage.  When below the bar storage constraint occurs, the
           abends RC00E20003, RC00E20013, RC00E20016, or RC00E70005 may
           occur at the next storage request.

        If you have already installed or migrated to DB2 10 then after
        applying this PTF, you need to take the following actions:
        (1) Update customized copies of DB2 installation CLIST members
        (2) Copy updated DB2 installation panels to alternate libraries
        (3) Optionally modify the DSMAX parameter setting
        Detailed guidance for these actions follows:

        ----------------------------------------------------------------
        (1) Update customized copies of DB2 installation CLIST members
        ----------------------------------------------------------------
        ==> This action is required for all DB2 10 customers

            This PTF modifies CLIST members 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) Copy updated DB2 installation panels to alternate libraries
        ----------------------------------------------------------------
        ==> This action is required if you maintain copies of the DB2
            installation panels outside of SMP/E:

            This PTF modifies DB2 installation panel DSNTIPC in the
1           prefix.SDSNSPFP target library.  If you keep the DB2
            installation panels in a different library then after
            applying this PTF, you need to copy the updated DSNTIPC
            panel to that library.

        ----------------------------------------------------------------
        (3) Optionally modify the DSMAX parameter setting
        ----------------------------------------------------------------
        ==> This action is required only if you want to change the DSMAX
            setting used by DB2:

            After applying this PTF, edit your customized copy of
            job DSNTIJUZ as follows:
            * Follow the recommendations noted earlier
            * Add or update the DSMAX keyword parameter with an integer
              setting of 1 to 200000 to the invocation of the DSN6SPRM
              macro.  Make sure to add a continuation character in
              column 72 if needed.  If the DSMAX parameter is not
              specified, it will be set to the default value of 20000
              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.
            * If you change the DSMAX setting, you should also update
              the OVDSMAX entry in the DB2 10 CLIST (DSNTIDxx) file
              for this DB2.  Edit the DSNTIDxx file, locate the
              OVDSMAX entry, and set the last field (indicated by <x>
              below) to your DSMAX value from DSNTIJUZ:
                OVDSMAX  CHAR  M  NONE        NONE          <x>
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNTINST  PM88166
       DSNTIPC   PM88166
       DSN6SPRM  PM88166

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88166   DSNTINST DSNTIPC  DSN6SPRM

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MACROS
       DSNTINST
       DSNTIPC
       DSN6SPRM

      LISTEND
 UK96368 COVER LETTER END


 UK96377 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90705 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of queries which   *
        *                 use hybrid join.                             *
1       ****************************************************************
        * PROBLEM DESCRIPTION: An incorrect result can be returned for *
        *                      a query that contains an aggregate      *
        *                      function, a GROUP BY, and uses hybrid   *
        *                      join.                                   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An incorrect result can be returned for a query that contains an
        aggregate function, a GROUP BY, and uses hybrid join.  The
        problem occurs if during query execution, a RID POOL overflow
        occurs.

        The following example will help to illustrate a failing case.

        If the access path chosen for this query is hybrid join on the
        inner table, a RID POOL overflow might occur when reading the
        RIDs for the inner table.

          SELECT B.COL1, SUM(B.COL2 * A.COLA) AS TOT, COUNT(*) AS COUNT
          FROM TABLEA A INNER JOIN TABLEB B ON B.COL3 = A.COLB
          WHERE A.COLC = 'PA'
              AND A.COLD = 'HE'
              AND B.COL1 =89
          GROUP BY B.COL1  ;

        Please note the following results.  The count of the number of
        qualified rows is less than expected as is the total sum.

        The failing result.
           +---------------------------------------------------+
           |  COL1    |   TOT                 |     COUNT      |
           +---------------------------------------------------+
         1_|       89 |            116806.910 |           3643 |
           +---------------------------------------------------+

        The expected result.
           +---------------------------------------------------+
           |  COL1    |   TOT                 |     COUNT      |
           +---------------------------------------------------+
         1_|       89 |           1904964.590 |          16697 |
           +---------------------------------------------------+

        The code in DB2 which processes a RID POOL overflow when set
        functions are involved has been modified to not reinitialize the
        set function (i.e. accumulators for aggregate functions) if the
        RID PHASE needs to be repeated.  This will prevent the loss of
        rows.

        Additional Keywords: SQLINCORROUT SQLINCORR DB2INCORR/K
                             SQLHYBRID SQLHYBRIDJOIN HYBRIDJOIN
                             SQLCOUNT SQLSUM SQLGROUPBY

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM90705
    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
       DSNXRGBJ  PM90705
       DSNXRSGB  PM90705

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90705   DSNXRGBJ DSNXRSGB

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXRGBJ
       DSNXRSGB

      LISTEND
 UK96377 COVER LETTER END


 UK96399 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89971 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9, DB2 10 and DB2 11 for z/OS        *
        *                 users of a query that references a           *
        *                 view that was created in DB2 Version 7.      *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABND04E 00E70005 at DSNXOSR P020        *
        *                      may occur for a query that references   *
        *                      a Version 7 view and the query          *
        *                      requires a sort such as with GROUP BY.  *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        ABND04E 00E70005 at DSNXOSR P020 may occur for a query that
        references a Version 7 view and the query requires a sort
        such as with GROUP BY.
        DB2 was fixed to correct the query that references a version
        7 view correctly.

        Additional Keywords: SQLVIEW SQLSORT

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89971
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOV0   PM89971

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89971   DSNXOV0

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1
      MODULES
       DSNXOV0

      LISTEND
 UK96399 COVER LETTER END


 UK96420 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM87503 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS, DB2 10 for z/OS and DB2  *
        *                 11 for z/OS utility users of RUNSTATS        *
        *                 TABLESPACE REPORT YES                        *
        ****************************************************************
        * PROBLEM DESCRIPTION: MSGDSNU626I contains a truncated column *
        *                      name for RUNSTATS TABLESPACE REPORT YES *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        When RUNSTATS TABLESPACE INDEX ALL REPORT YES was issuing the
        MSGDSNU626I message(s), a column name that was at the very end
        of the message line was truncated by 1 to 3 characters,
        depending on how close to the end of the output line it was.

        This occurred because RUNSTATS code used a wrong message line
        length.
        RUNSTATS code has been changed to use the correct length when
        calculating the placement of column names for the DSNU626I
        message.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM87503
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUSUPD  PM87503

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM87503   DSNUSUPD

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUSUPD

      LISTEND
 UK96420 COVER LETTER END


 UK96423 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90046 -
        ****************************************************************
1       * USERS AFFECTED: All DB2 9, 10 for z/OS users of XML.         *
        ****************************************************************
        * PROBLEM DESCRIPTION: The following may occur when inserting, *
        *                      updating, or loading XML data:          *
        *                                                              *
        *                      ABEND0C4 RC00E70005 in module DSNNXDLC  *
        *                      offsetM660                              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        DB2 called z/OS XMLSS to parse XML data and XMLSS terminated
        abnormally.  During DB2 clean up, the z/OS XMLSS call GXL4TRM
        returned reason code XRSN_PIMA_NOT_INITIALIZED ('1000'x) which
        caused DB2 to abend and required a restart of DB2.
        The DB2 for z/OS code was modified to fix the abend problem
        when GXL4TRM returns reason code '1000'x during DB2
        deallocation.

        Additional keywords: XMLALL DB2ABTERM SQLXML
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM90046
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNNXDLC  PM90046

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90046   DSNNXDLC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNNXDLC

      LISTEND
 UK96423 COVER LETTER END


 UK96439 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90509 -
        ****************************************************************
        * USERS AFFECTED: DB2 users.                                   *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C90101 in DSNIBHRE during  *
        *                      DB2 restart (with various ERQUALs).     *
        *                                                              *
        *                      Inconsistent data after a DB2 crash     *
        *                      and restart, which can result in any    *
        *                      of the following symptoms:              *
        *                       - Incorrect output, INCORROUT.         *
        *                       - ABEND04E RC00C90101, RC00C90102,     *
        *                         RC00C90105, or RC00C902xx in         *
        *                         various CSECTs.                      *
1       *                       - Data/index inconsistencies reported  *
        *                         by the CHECK INDEX utility.          *
        *                       - Page regression reported by the      *
        *                         DSN1LOGP utility.                    *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        A timing window exist in the process of converting a table space
        or index from read-only to read/write, in which it is possible
        for an agent to write a second "pageset open" or "dataset 
open"
 
        log record after another agent had already logged an update to
        the object.  If DB2 were to crash and restart after that point,
        the existence of the second open log would cause the log record
        for the first update to be skipped.  This may cause a later log
        apply error, with an ABEND04E RC00C90101 in DSNIBHRE, or it may
        result in other "broken data" symptoms later on.
        The process of converting a table space or index to read/write
        has been modified to get the conversion lock earlier, so that it
        will serialize the writing of the open log record.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM90509
    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  PM90509

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90509   DSNB1SWS

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNB1SWS

      LISTEND
 UK96439 COVER LETTER END


 UK96441 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89734 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS      *
        *                 users of Flashcopy Image COPY utility and    *
        *                 COPYTOCOPY utility.                          *
        ****************************************************************
        * PROBLEM DESCRIPTION: MSGIEC161I 072-053 (OPEN OF AN EMPTY    *
        *                      DATA SET) and ABEND04E RC00E40070       *
        *                      (DB2 OPEN FAILURE) during COPY and      *
        *                      COPYTOCOPY utilities on a               *
        *                      non-partitioned object when one or      *
        *                      more linear pieces are empty and DSNUM  *
        *                      ALL is specified.                       *
        ****************************************************************
1       * RECOMMENDATION:                                              *
        ****************************************************************
          User ran LOAD REPLACE utility with an empty input data set
        on a multi-piece linear object as a means to clear the data.
        The REUSE keyword was specified on the LOAD statement so
        that all data sets would be retained, even though all but
        the first were now empty.
          The user then made a Flashcopy Image Copy (FCIC) of the
        object using COPY utility with DSNUM ALL.  The FCIC
        included all data sets created for the object, including
        the empty ones.
          Finally, COPYTOCOPY utility was run with DSNUM ALL to make
        a sequential copy from the FCIC.  The job abended with
        ABEND04E RC00E40070 and also message IEC161I 072-053,
        indicating an OPEN request was made for an empty data set
        (HI-U-RBA was zero).
          The same problem was also seen when COPY utility was run
        with DSNUM ALL on a multi-piece linear object with empty
        piece(s) when an FCIC and a sequential output data set were
        requested in the same invocation.  The abend occurred
        during the processing of the sequential output data set.
          Code was changed in DB2 COPY and COPYTOCOPY utilities and
        utility general services to properly handle OPEN errors due to
        empty data sets when DSNUM ALL is specified.
          Note that even with this fix applied, message IEC161I will
        still be seen in this scenario since it is issued outside
        of DB2 as a result of the OPEN request for an empty data set.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89734
    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  PM89734
       DSNUGSDA  PM89734
       DSNU2BCC  PM89734

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89734   DSNUBBID DSNUGSDA DSNU2BCC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUBBID
       DSNUGSDA
       DSNU2BCC

      LISTEND
 UK96441 COVER LETTER END


 UK96443 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90037 -
        ****************************************************************
1       * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS       *
        *                 users who have migrated, or plan to migrate, *
        *                 their systems to a level at or above DB2 9   *
        *                 NFM for the first time, followed by a        *
        *                 conversion to data sharing.                  *
        ****************************************************************
        * PROBLEM DESCRIPTION: MSGDSNB232I issued in error upon        *
        *                      first open of an object following       *
        *                      migration to DB2 9 NFM or above         *
        *                      and subsequent conversion to data       *
        *                      sharing.                                *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        User's scenario was as follows:
        1. a non-data sharing system was migrated from DB2
        Version 8 to DB2 10 NFM (new function mode).
        2. some time later, the system was converted to data
        sharing.
        3. the system RBA was numerically greater than the
        STCK (clock time) at the time of the conversion.
        4. an operation resulting in an OPEN of the data set (e.g.,
        SQL update) failed with
        DSNB232I = UNEXPECTED DATA SET LEVEL ID ENCOUNTERED.

        The false detection was due to code that didn't properly
        handle all of the factors above.  The user's object was not
        downlevel and their data was not compromised.
        Code was added to utility general services to bypass
        down level detection (DLD) checking in the circumstances
        described above.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM90037
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUAHR2  PM90037

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90037   DSNUAHR2

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUAHR2

      LISTEND
 UK96443 COVER LETTER END


 UK96451 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89142 -
        ****************************************************************
1       * USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS      *
        *                 utility users of LOAD INCURSOR from a table  *
        *                 with ASCII CCSID 943                         *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABENDS0C4 at DSNURELD +x'5C32' occurs   *
        *                      with LOAD INCURSOR with CCSID           *
        *                      translation from CCSID 943              *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        LOAD INCURSOR from a table defined with CCSID 943 with CCSID
        translation to the CCSID of the target table results in
        an ABEND0C4 at DSNURELD OFFSET5C32.  The abend occurred because
        a pointer to a control block had not been set correctly which
        resulted in non-allocated storage being referenced.
        LOAD INCURSOR code has been changed to correctly reference the
        aforementioned control block.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89142
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNURELD  PM89142

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89142   DSNURELD

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNURELD

      LISTEND
 UK96451 COVER LETTER END


 UK96463 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM84683 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 for z/OS.                   *
        ****************************************************************
        * PROBLEM DESCRIPTION: 1. ABEND04E RC00C90101 DSNIZLDR         *
        *                      ERQUAL5002 during DB2 restart.          *
        *                                                              *
        *                      2. DB2 will not restart due to lock not *
        *                      being released from abend.  Message     *
        *                      MSGDSNR056I is generated periodically   *
        *                      during restart.                         *
        *                                                              *
        *                      DSNR056I  @ DSNRTIMR RESTART SUSPENDED  *
        *                      ON IRLM REQUEST. ONE HOLDER OF RESOURCE *
        *                      IS SUBSYSTEM ********.                  *
        *                      SERVICE INFO: IRLM FUNC 02,             *
1       *                      RESOURCE 0C0000070112000200000000       *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        DB2 crashed before the dictionary pages were written to
        disk.  However, the "dictionay complete" state that is
        maintained in the header page was updated AND written
        to disk.

        During DB2 restart buffer manager requested the dictionary
        be loaded in memory (due to the "dictionary complete" state
        in the header page).

        The abend occurs because the dictionary page was not recovered
        yet, and did not contain the correct dictionary control block
        information.

        DB2 could not complete restart because the previous abend
        did not have sufficient program recovery to release the
        lock.
        DB2 has been modified to recognize when the load dictionay
        process is in DB2 restart and not abend.  Instead of abending
        DB2 will produce a DSNT501I resource not available message,
        release any held resources, and then continue restart.

        After DB2 has been restarted and the dictionary pages recovered,
        an invalid dictionary page will then result in an abend.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM84683
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNIZLDR  PM84683

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM84683   DSNIZLDR

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIZLDR

      LISTEND
 UK96463 COVER LETTER END


 UK96469 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90188 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 and 11 for z/OS user of SQL       *
        *                 statement containing EXISTS predicate in     *
        *                 WHEN clause of CASE expression.              *
        ****************************************************************
1       * PROBLEM DESCRIPTION: A non-optimal access path may be        *
        *                      selected when an SQL statement          *
        *                      satisfies all of the following          *
        *                      conditions:                             *
        *                                                              *
        *                      1. EXISTS predicate is used in WHEN     *
        *                         clause of CASE expression;           *
        *                      2. multiple tables are referenced in    *
        *                         FROM clause.                         *
        *                      3. predicate transitive closure happens *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        A non-optimal access path may be selected when an SQL statement
        satisfies all of the following conditions:

        1. EXISTS predicate is used in WHEN clause of CASE expression;
        2. multiple tables are referenced in FROM clause.
        3. predicate transitive closure happens.

        The following example helps to illustrate problem:
        SELECT CASE
                 WHEN EXISTS (SELECT 1 FROM SYSIBM.SYSDUMMY1)
                   THEN 1
                 ELSE 0
               END AS COL1
        FROM TAB1 AS A,
             TAB2 AS B,
             TAB3 AS C
        WHERE A.C1 = B.C1
              AND B.C2. = C.C2
              AND A.C1 = 11
              AND B.C2 = 22;

        The join sequence or join method may not be optimal selected
        when EXISTS predicate appears in WHEN clause of CASE expression.
        Code in DB2 has been correctly modified to handle EXISTS
        predicate in WHEN clause of CASE expression.

        Additional keyword: SQLCASE SQLEXISTS SQLACCESSPATH
                            SQLPERFORMANCE

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM90188
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM90188:

        See PM90188 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM90188 corrects a problem of non-optimal access path may be
        selected when an SQL statement satisfies all of the following
        conditions:
1
        1. EXISTS predicate is used in WHEN clause of CASE expression;
        2. multiple tables are referenced in FROM clause;
        3. predicate transitive closure happens.

        To make this fix effective for a static application, it must 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  PM90188
       DSNXOTCP  PM90188

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90188   DSNXOEXT DSNXOTCP

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOEXT
       DSNXOTCP

      LISTEND
 UK96469 COVER LETTER END


 UK96475 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM93588 -
        ****************************************************************
        * USERS AFFECTED: All data sharing users of DB2 for zOS.       *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C90101 ERQUAL5007 in       *
        *                      DSNIDEFR while running a RECOVER        *
        *                      TOLOGPOINT utility in a data sharing    *
        *                      environment.                            *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The abend in DSNIDEFR occurred when attempting to read an
        LRSN range beyond the end of the log for a quiesced member
        of the data sharing group.  No log records were returned
        for this member and DSNIDEFR issued the abend when an RC04
        RC00D10320 was received on the log read request.  This
        occurred as there was an open SYSLGRNX range for the object
        being recovered on this quiesced member.  DSNIDEFR was
        reading the log backwards until a checkpoint is found.
        DSNJR103 has been changed to start reading from the end of
        the quiesced member's logs in this situation.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM93588
    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
       DSNJR103  PM93588

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM93588   DSNJR103

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNJR103

      LISTEND
 UK96475 COVER LETTER END


 UK96523 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89998 -
        ****************************************************************
        * USERS AFFECTED: DB2 9, 10, 11 for z/OS users of CREATE TABLE *
        ****************************************************************
        * PROBLEM DESCRIPTION: User receives ABND=04E-00C90101,        *
        *                      LOC=DSNGD001.DSNGDVRT:5005 from         *
        *                      CREATE TABLE or other DDL statements.   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        ABND=04E-00C90101,LOC=DSNGD001.DSNGDVRT:5005 occurs during
        CREATE TABLE processing if a nullable VARCHAR(32767) column is
        one of the definitions included. This abend also occurs in the
        following scenarios:
         - CREATE MATERIALIZED QUERY TABLE
             with a nullable VARCHAR(32767) column
         - CREATE TABLE LIKE TABLE/VIEW
             with a nullable VARCHAR(32767) column
         - CREATE GLOBAL TEMPORARY TABLE LIKE
             TABLE/VIEW with a nullable VARCHAR(32767) column
         - DECLARE GLOBAL TEMPORARY TABLE LIKE
             TABLE/VIEW with a nullable VARCHAR(32767) column
        This abend occurs because DB2 incorrectly calculates the table
        record length with this column definition.
        DB2 has been modified to correctly calculate the table record
        length. With this APAR applied, DB2 will return SQLCODE -670
        when attempting any of the affected statements with a nullable
        VARCHAR(32767) column.

        Additional Keywords:
        SQLCREATE
        SQLNULL
        ABEND04E
        RC00C90101
        SQLCODE670
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89998
    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
       DSNXICB1  PM89998
       DSNXISB4  PM89998

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89998   DSNXICB1 DSNXISB4

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXICB1
       DSNXISB4

      LISTEND
 UK96523 COVER LETTER END


 UK96548 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM91243 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS, DB2 10 for z/OS and      *
        *                 DB2 11 for z/OS users of a query referencing *
        *                 a partition-by-growth table.                 *
        ****************************************************************
        * PROBLEM DESCRIPTION: An ABEND0C4 RC00000010 at               *
        *                      DSNSLD1.DSNSVBK may occur when running  *
        *                      a query referencing a                   *
        *                      partition-by-growth table. After the    *
        *                      abend, DB2 may also be brought down.    *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An ABEND0C4 RC00000010 at DSNSLD1 .DSNSVBK may occur when
        running a query referencing a partition-by-growth table. After
        the abend, DB2 may also be brought down.

        It is because when running such query, a storage overlay may
        occur due to wrongly referencing an array index when retrieving/
        updating data for a partition-by-growth table. If the storage
        overlay happens at the critical storage control block
        information area, it can further bring down DB2.

        Following is an example of a failing query:

        EXPLAIN PLAN SET QUERYNO = 1 FOR
        SELECT EMPNO, FIRSTNME, SALARY
          FROM FINAL TABLE
          ( MERGE INTO EMP AS EMP2
            USING ( VALUES ('123456', 'ABCDE' ,11111))
            AS T (EMPNO, FIRSTNME, SALARY)
            ON (EMP2.FIRSTNME = T.FIRSTNME)
            WHEN MATCHED THEN UPDATE
            SET SALARY = EMP2.SALARY + 100
1           WHEN NOT MATCHED THEN INSERT
            (EMPNO,FIRSTNME,MIDINIT,LASTNAME,WORKDEPT,SALARY)
            VALUES ('123456','ABCDE',' ','WXYZ','ABC',11111)
          );

        DB2 is modified to reference the correct array index to prevent
        a storage overlay.

        Additional Keywords: SQLSTORAGE DB2OVRLAY/K PBG UTS ABEND0C4
                             RC00000010
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM91243
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM91243:

        See PM91243 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM91243 corrects a problem of ABEND0C4 RC00000010 at
        DSNSLD1.DSNSVBK when running a query referencing a
        partition-by-growth table.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM75044:

        See PM75044 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM75044 corrects the conditions that can lead to the
        occurrence of an ABEND04E RC00E72018 at DSNXSZK OFFSET 2DBE
        when executing a query with group by, running with parallelism.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        See PM69950 APAR/PTF text in the PTF cover letter for
        additional information about why a REBIND is necessary.

        Apar PM69950 corrects the conditions that can lead to the
        occurrence of an ABEND04E RC00C90101 at location DSNOTCSO:5020
        when executing a query that contains a select that references a
        HAVING clause with a LOB, but without a group by and set
        function, running with parallelism.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
1       affected by this change.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOCN   PM91243
       DSNXOLCM  PM91243
       DSNXOLM1  PM91243
       DSNXOTPL  PM91243

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM91243   DSNXOCN  DSNXOLCM DSNXOLM1 DSNXOTPL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOCN
       DSNXOLCM
       DSNXOLM1
       DSNXOTPL

      LISTEND
 UK96548 COVER LETTER END


 UK96551 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89599 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 and DB2 11 users who get          *
        *                 incorrect SQLCODE -203.                      *
        ****************************************************************
        * PROBLEM DESCRIPTION: SQLCODE -203 is incorrectly issued      *
        *                      when a built-in scalar function         *
        *                      requires a keyword, but tables used     *
        *                      in the queries have columns with the    *
        *                      same name as the keyword.               *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        SQLCODE -203 is incorrectly issued by DB2 when a query uses
        a built-in scalar function that requires a keyword, but there
        are tables referenced in the query that have the same names
        as the required keyword. This can happen when multiple tables
        are referenced in the same SQL statement that have columns
        with the same name as a keyword.

        For example:

        CREATE TABLE T1 (DATECOL DATE, ISO CHAR(1));
        CREATE TABLE T2 (DATECOL DATE, ISO CHAR(1));

        SELECT CHAR(T1.DATECOL, ISO)
        FROM T1, T2
        WHERE T1.DATECOL=T2.DATECOL;

        This SELECT statement incorrectly gets SQLCODE -203.
        ISO is used as a keyword for the CHAR function,
1       but there are also columns named ISO in the two tables
        referenced.

        Keywords also may be used in the following
        built-in scalar functions:

        CHAR
        CHARACTER_LENGTH
        CLOB
        DBCLOB
        DECRYPT_BINARY
        DECRYPT_BIT
        DECRYPT_CHAR
        DECRYPT_DB
        GRAPHIC
        INSERT
        LEFT
        LOCATE
        LOCATE_IN
        NORMALIZE
        OVERLAY
        POSITION
        RIGHT
        STRIP
        SUBSTRING
        TRIM
        UNICODE_STR
        VARCHAR
        VARGRAPHIC

        The keywords that may be used in those functions include:

        CODEUNITS16
        CODEUNITS32
        OCTETS
        ISO
        USA
        EUR
        JIS
        LOCAL
        DEFAULT
        NFC
        NFD
        NFKC
        NFKD
        BOTH
        B
        LEADING
        L
        TRAILING
        T
        DB2 code is changed to not issue the incorrect SQLCODE -203.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89599
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
1                LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        See PM83404 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM83404 corrects a problem of ABEND04E RC00E70005 in DSNXRSBC
        P016 when the GETHINT built-in function is used to retrieve
        the hint for the password with which the data of a NOT NULL
        column were encrypted but there was no hint specified during
        data encryption.

        To make this fix effective for a static application, it must 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:
        PM83404 corrects a problem of ABEND04E RC00E70005 in DSNXRSBC
        P016 when the GETHINT built-in function is used to retrieve
        the hint for the password with which the data of a NOT NULL
        column were encrypted but there was no hint specified during
        data encryption.

        To make this fix effective for any view, column mask, or row
        permission defined on expressions that contain the GETHINT
        function, the object must be regenerated using the ALTER VIEW
        REGENERATE, ALTER MASK REGENERATE, or ALTER PERMISSION
        REGENERATE statement, respectively, or dropped and recreated
        after application of this PTF.

        To make this fix effective for any MQT, SQL scalar UDF, or
        index defined on expressions that contain the GETHINT
        function, the object must be dropped and recreated after
        application of this PTF.

        After application of the PTF, the nullability of the GETHINT
        scalar function may be different. Applications using DESCRIBE
        may be impacted. Proper actions should be taken if such impact
        is observed.

        If the DSNTIAUL sample program is used correctly to generate a
        LOAD utility control statement, then after application of this
        PTF, the new control statement generated may not match the
        nullability of the GETHINT scalar functions from the previous
        control statement. Proper action should be taken if such
        mismatch is observed.

        This PTF affects the nullability of the GETHINT built-in scalar
        function returned by dynamic SQL processing programs, such as
        SPUFI, DSNTEP2, and DSNTEP4. Proper actions should be taken
        if such change is observed.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOBFA  PM89599
       DSNXOBFF  PM89599
       DSNXORSO  PM89599

1     CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89599   DSNXOBFA DSNXOBFF DSNXORSO

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOBFA
       DSNXOBFF
       DSNXORSO

      LISTEND
 UK96551 COVER LETTER END


 UK96595 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM91546 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS data sharing users with     *
        *                 PM53155 that need to apply its PE fixing     *
        *                 APAR PM77066 without applying enabling       *
        *                 APAR PM74803.                                *
        *                                                              *
        *                 PTFs for the above mentioned APARs:          *
        *                   PM53155 / UK77362 for DB2 10 for z/OS      *
        *                   PM53155 / UK77364 for DB2 9 for z/OS       *
        *                   PM53155 / UK77363 for DB2 V8 for z/OS      *
        *                                                              *
        *                   PM77066 / UK91321 for DB2 10 for z/OS      *
        *                   PM77066 / UK91323 for DB2 9 for z/OS       *
        *                   PM77066 / UK91322 for DB2 V8 for z/OS      *
        *                                                              *
        *                   PM74803 / UK90830 for DB2 10 for z/OS      *
        *                   PM74803 / UK90832 for DB2 9 for z/OS       *
        *                   PM74803 / UK90831 for DB2 V8 for z/OS      *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNIDBHK ERQUAL500C *
        *                      during several data sharing members'    *
        *                      DB2 checkpoint after group restart,     *
        *                      leading to their DB2 crash with         *
        *                      MSGDSNV086E RC00D95001                  *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        During group restart, while updating the group DBET in SCA,
        a subset of the DBET base SCA record(s) for an object was
        accidentally deleted, which resulted in local DBET entry for the
        object being built incorrectly.

        In this case, there were more than 200 partitions with diverse
        exception states such that the DBET entry for this object had
        multiple DBET blocks. During internal DBET rectify, at the
        beginning of forward log apply phase, the group DBET in SCA
        needed to be updated since local DBET had to reset an internal
        extend-in-progress state.

1       However, when copying the local DBET blocks to the group DBET in
        SCA, by mistake not all the DBET blocks were copied. This
        resulted in an incomplete group DBET in SCA for this object.

        When other members of the data sharing group came up, their
        local DBET was built incorrectly, eventually leading to the
        aforementioned ABEND04E.

        The first member that performed the rectify was able to come
        up successfully because his local DBET was not corrupted. Any
        subsequent DBET updates that this member performed after the
        group restart automatically cleaned up the group DBET in SCA,
        which is why the originally failed members were able to restart
        on their second restart attempt.
        DB2 code has been modified such that the group DBET in SCA is
        updated correctly during DBET rectify.

        Upcoming APAR, PM91547 will enable APAR PM69760.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM91546
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      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
       DSNIDBEL  PM91546
       DSNIDBGN  PM91546
       DSNIDBGR  PM91546
       DSNIDBNG  PM91546
       DSNIDBNI  PM91546

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM91546   DSNIDBEL DSNIDBGN DSNIDBGR DSNIDBNG DSNIDBNI

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIDBEL
       DSNIDBGN
       DSNIDBGR
       DSNIDBNG
       DSNIDBNI

      LISTEND
1UK96595 COVER LETTER END


 UK96619 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM87446 -
        ****************************************************************
        * USERS AFFECTED: DB2 users of stored procedures and           *
        *                 User Defined Functions (UDFs).               *
        *                                                              *
        ****************************************************************
        * PROBLEM DESCRIPTION: Stored procedure threads cannot         *
        *                      be terminated after going to EOT        *
        *                      if the thread is waiting for a reply    *
        *                      from a remote location via TCP/IP       *
        *                      connection.                             *
        *                                                              *
        *                      In this case, if the address space is   *
        *                      forced down, DB2 will terminate with    *
        *                      ABEND30D RC00F30411.                    *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        If an stored procedure thread is waiting for a reply
        from a remote location, the thread cannot be terminated
        when it goes to EOT. This is because currently in EOT
        processing there is no mechanism to terminate the TCP/IP
        connections and therefore the cancel operation
        that causes the EOT cannot be fully honored.
        DSNX9TRE
        DB2 code has been enhanced so that it can terminate the
        connections in case the thread is in DDF waiting for reply.
        This will allow DB2 to complete the stored procedure thread
        termination.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM87446
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNX9TRE  PM87446

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM87446   DSNX9TRE

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNX9TRE

      LISTEND
 UK96619 COVER LETTER END


 UK96625 COVER LETTER START
1   PROBLEM DESCRIPTION(S):
      PM89587 -
        ****************************************************************
        * USERS AFFECTED: All DB2 users of the IBM DB2 Analytics       *
        *                 Accelerator for z/OS, BIND PLAN with PKLIST, *
        *                 and special register CURRENT PACKAGESET      *
        ****************************************************************
        * PROBLEM DESCRIPTION: When using the IBM DB2 Analytics        *
        *                      Accelerator (IDAA) to accelerate DB2    *
        *                      queries, DB2 issued SQLCODE -805 with   *
        *                      reason code 02  and the SQLCA message   *
        *                      token SQLERRM shows an IDAA accelerator *
        *                      name as the location name in the fully  *
        *                      qualified package name --               *
        *                                                              *
        *                       accelerator-name.collid.package-name   *
        *                                                              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        If all of the following apply when running an application:
         (1) either special register CURRENT QUERY ACCELERATION or DB2
             Installation parameter (aka zparm) QUERY_ACCELERATION is
             used to request that DB2 accelerate the application's query
             to the IBM DB2 Analytics Accelerator ( IDAA ), and
         (2) the application uses special register CURRENT PACKAGESET to
             specify the collection-id that DB2 should use for
             the application/package, and
         (3) BIND PLAN with a PKLIST specification was previously done
             for the application's associated plan, where location '*'
             was not used as part of the PKLIST collection-id entry for
             the application's package that issues the dynamic queries
             to be accelerated to IDAA, as shown in these PKLIST
             examples --
               PKLIST (collid1.*, collid2.*, ...)   or
               PKLIST (collid1.pkgname, collid2.pkgname, ...)   or
               PKLIST (location-name.collid.*, ... ) or
               PKLIST (location-name.collid.pkgname, ...)
                                                                       .
        then, DB2 issued SQLCODE -805 with reason code 02 when user
        attempted to run that application/package. In the returned SQLCA
        the SQLERRP = DSNXEPM and the SQLERRM message tokens show
        a fully qualified package name where the location name is
        the name of an IDAA accelerator --
           accelerator-name.collid.package-name
                                                                       .
        The SQLCODE805 is an invalid failure in this scenario, and
        DB2 should not require the accelerator name as the location name
        in the target collection-id entry of the PKLIST when doing
        query acceleration to IDAA.
                                                                       .
        This error only occurs when CURRENT PACKAGESET is used in
        the described scenario.  If CURRENT PACKAGESET is not used,
        the query is accelerated to IDAA.  To circumvent the problem,
        one of the following can be done:
         - if applicable, in the PKLIST on BIND / REBIND PLAN specify
1          a location name of '*' in the collection-id entry for
           the package that is issuing the accelerated query, as
           shown in the following examples:
             BIND / REBIND PLAN (...) PKLIST (*.collid.* , ...) or
                                             (*.collid.package-name)
           and reissue the BIND / REBIND PLAN w/ PKLIST (no REBIND of
           the package is needed),  OR
         - if removal of the SET CURRENT PACKAGESET can be done
           successfully, then remove that SET. This will avoid
           the problem, even leaving the original PKLIST specification
           'as is'.
        DB2 code was corrected to not issue SQLCODE805 for the
        previously described scenario where both CURRENT PACKAGESET and
        BIND PLAN with PKLIST are used and a query is accelerated to
        to the IBM DB2 Analytics Accelerator.
                                                                       .
        Additional search keywords: IDAAV2R1/K IDAAV3R1/K
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89587
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXEPM   PM89587

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89587   DSNXEPM

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXEPM

      LISTEND
 UK96625 COVER LETTER END


 UK96630 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM87230 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users who use graphic    *
        *                 host variable in SBCS system.                *
        ****************************************************************
        * PROBLEM DESCRIPTION: SQLCODE -332 is issued when following   *
        *                      conditions are true.                    *
        *                      1. The value of the field MIXED DATA    *
        *                         on installation panel DSNTIPF is NO. *
        *                      2. The table or view is EBCDIC or       *
        *                         ASCII, or the application encoding   *
        *                         scheme is EBCDIC or ASCII.           *
        *                      3. The statement references a graphic   *
        *                         host variable.                       *
        ****************************************************************
        * RECOMMENDATION:                                              *
1       ****************************************************************
        SQLCODE -332 may be issued when the following conditions are
        true:

        1. The value of the field MIXED DATA on installation panel
           DSNTIPF is NO.
        2. The table or view is EBCDIC or ASCII, or the application
           encoding scheme is EBCDIC or ASCII.
        3. The statement references a graphic host variable.

        When the table or view is EBCDIC or ASCII and the value of the
        MIXED DATA on installation panel DSNTIPF is NO, the encoding
        scheme of the statement is EBCDIC or ASCII, and the graphic
        host variable in the statement is processed in EBCDIC or ASCII.
        However, there is no double byte CCSID for the graphic host
        variable because of MIXED DATA = NO. This causes SQLCODE -332
        to be issued when conversion for this graphic host variable is
        needed.

        For example:
          Assume that table TESTU000 is defined with CCSID EBCDIC, and
          contains the following columns:
            C1 SMALLINT
            C2 CHAR(40)
            C3 CHAR(40)

          Assume that the application is COBOL with the following
          declarations:
            TESTU000-C1E PIC S9(5) COMP-5.
            TESTU000-C2E PIC X(40).
            TESTU000-C3E PIC X(40).
            TESTU000-C2N PIC N(40) USAGE NATIONAL.

          The TESTU000-C2N will be mapped by DB2 as a graphic host
          variable.

          The SQL statement below has a predicate references the graphic
          variable TESTU000-C2N and the character column C2 in table
          TESTU000 which is defined with CCSID EBCDIC.

            SELECT C1, C2, C3
              INTO :TESTU000-C1E,
                   :TESTU000-C2E,
                   :TESTU000-C3E
            FROM TESTU000
            WHERE C2 = :TESTU000-C2N

        SQLCODE -332 will be issued when this SQL statement is bound,
        because there is no double byte CCSID for the graphic host
        variable TESTU000-C2N.

        The similar problem occurs when a statement is processed as a
        multiple encoding scheme statement and the statement is bound
        with BIND option ENCODING(EBCDIC) or ENCODING(ASCII).

        A graphic host variable is a variable that is mapped to DB2
1       GRAPHIC, VARGRAPHIC, and DBCLOB data type.
        To avoid SQLCODE -332 as shown in the above example, starting
        in DB2 10 New Function Mode (NFM), DB2 will use Unicode encoding
        scheme for the graphic host variable when the field MIXED DATA
        on installation panel DSNTIPF is NO and:

        1. the statement is a EBCDIC or ASCII encoding scheme statement,
        or
        2. the statement is a multiple encoding scheme statement and the
           application encoding scheme is EBCDIC or ASCII.

        Also starting in DB2 10 NFM, if such a graphic host variable is
        referenced in the statement, the comparison rule or the result
        data type rule that involves a graphic operand will use the
        column's CCSID (or the derived value based on a column's CCSID)

        Additional keywords: SQLCCSID SQLGRAPHIC SQLVARGRAPHIC
                             SQLENCODING
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM87230
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        See PM87230 APAR/PTF text in the PTF cover letter for
        additional information about why a REBIND is necessary.

        Starting in DB2 10 New Function Mode (NFM), this APAR changed
        the encoding scheme for the graphic host variable (GRAPHIC,
        VARGRAPHIC, or DBCLOB) when the value of the field MIXED DATA
        on installation panel DSNTIPF is NO and:

        1. the statement is a EBCDIC or ASCII encoding scheme statement,
        or
        2. the statement is a multiple encoding scheme statement and the
           application encoding scheme is EBCDIC or ASCII.

        In the above statement the graphic host variable is processed in
        EBCDIC or ASCII, but there is no double byte CCSID assigned for
        the graphic host variable because of MIXED DATA = NO. This
        causes SQLCODE -332 to be issued when conversion for the graphic
        host variable is needed.

        To avoid SQLCODE -332, starting in DB2 10 NFM, this APAR sets
        the encoding scheme for the graphic host variable to Unicode
        encoding scheme when the field MIXED DATA on installation panel
        DSNTIPF is NO and:

        1. the statement is a EBCDIC or ASCII encoding scheme statement,
        or
        2. the statement is a multiple encoding scheme statement and the
           application encoding scheme is EBCDIC or ASCII.

        Also starting in DB2 10 NFM, if such a Unicode graphic host
        variable is referenced in the context with a column that follows
        the comparison rule or the result data type rule, the target
1       CCSID of the comparison or the result data type operation will
        use the column's CCSID (or the derived value based on a column's
        CCSID).

        In the SQL Reference, the new Note 2 has been added to the
        Table 36. "Operand that supplies the CCSID for character
        conversion" for the Host Variable operand as below.

        Note:
        2. If a graphic host variable is referenced in the statment,
           and the value of the field MIXED DATA on installation panel
           DSNTIPF is NO, the column or the derived value based on a
           column supplies the target CCSID set.

        To make this change effective for a static application in V10
        NFM, it must be rebound on V10 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
       DSNXOBFC  PM87230
       DSNXODTR  PM87230
       DSNXOP0   PM87230
       DSNXOTDA  PM87230

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM87230   DSNXOBFC DSNXODTR DSNXOP0  DSNXOTDA

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOBFC
       DSNXODTR
       DSNXOP0
       DSNXOTDA

      LISTEND
 UK96630 COVER LETTER END


 UK96647 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88876 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 and 10 for z/OS users run SELECT   *
        *                 query under CPU parallelism.                 *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C90101 at DSNIPSBL         *
        *                      ERQUAL003 or ERQUAL004 while running    *
        *                      SELECT statements under CPU parallelism *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        While CPU parallelism kicks out a parallel task where it must
        attempt to locate several, specific control blocks from the
        parent task. Without proper serialization, such locate process
1       may run into obsolete control blocks just released by the parent
        task and caused unnecessary abends.
        DB2 code is modified to do a proper serialization under CPU
        parallelism to ensure the locate process performed by the
        parallel task won't run into obsolete control blocks.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88876
    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  PM88876
       DSNIPSBL  PM88876
       DSNXPCRT  PM88876
       DSNXPDST  PM88876

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88876   DSNICMT2 DSNIPSBL DSNXPCRT DSNXPDST

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNICMT2
       DSNIPSBL
       DSNXPCRT
       DSNXPDST

      LISTEND
 UK96647 COVER LETTER END


 UK96651 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM91165 -
        ****************************************************************
        * USERS AFFECTED: All Distributed Data Facility ( DDF ) users  *
        *                 of Declared Global Temporary Tables (DGTTs)  *
        *                 where DB2 is configured with                 *
        *                 DDF THREADS=INACTIVE specified ( DSN6FAC     *
        *                 CMTSTAT INACTIVE )                           *
        ****************************************************************
        * PROBLEM DESCRIPTION: A user of a DB2 for z/OS remote server  *
        *                      thread ( DBAT ) inherits Declared       *
        *                      Global Temporary Tables ( DGTTs ) that  *
        *                      were created by a previous user of      *
        *                      this same DBAT, and the current user    *
        *                      of the DBAT encounters the following    *
        *                      unexpected DBAT symptoms and conditions *
        *                      due to those 'inherited' DGTTs:         *
        *                                                              *
        *                       o Messages DSNL027I and DSNL028I with  *
        *                         reason code 00D3003B .               *
        *                                                              *
        *                       o Over utilzation of DBATs, perhaps    *
        *                         leading to an erroneous MAXDBAT      *
1       *                         limit condition.                     *
        *                                                              *
        *                       o A quiesce stop of DDF may not        *
        *                         complete due to the erroneous        *
        *                         presence of an active DBAT.          *
        *                         A -STOP DDF MODE(FORCE) may be       *
        *                         necessary in order for DDF to        *
        *                         complete its STOP processing.        *
        *                                                              *
        *                       o The DBAT, now being accessed by      *
        *                         a new user, shows continued          *
        *                         lock on and usage of DGTT tablespace *
        *                         in the workfile database.            *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        A user configured DB2 for inactive threads and connection
        pooling for remote DB2 server threads (DBATs) via
        DDF THREADS=INACTIVE (or DB2 installation parm / zparm
        DSN6FAC CMTSTAT INACTIVE). On this same DB2 (as a server),
        a user ran one or more remote applications via a DBAT and these
        applications resulted in a mix of Declared Global Temporary
        Tables (DGTTs) defined with and without ON COMMIT DROP TABLE.
        These applications ended and intentionally left some DGTTs
        remaining, but DB2 then incorrectly allowed the associated DBAT
        (with its remaining DGTTs) to go 'inactive' at a COMMIT point
        and be pooled in the connection pool to be reused later as a
        DBAT to service other remote work/applications.  When DB2 later
        reused this same DBAT to service remote work for a 'different'
        user who did not use DGTTs, this new user 'inherited' the
        'previous' user's remaining DGTTs and experienced the reported
        DBAT symptoms and conditions previously described.
                                                                       .
        The unexpected DBAT conditions resulted from both
        (1) the 'new' user inheriting the remaining DGTTs created by
            a previous user of that same DBAT, and
        (2) DB2 then enforcing on this 'new' user the restriction that
            a DBAT that has active DGTTs cannot go inactive,
        thus giving this 'new' user the DBAT conditions that should have
        been issued for the 'previous' user of the DBAT but were not.
        Those DBAT conditions and messages would be valid for 'previous'
        user of this DBAT, but not for the 'new' user of the DBAT.
                                                                       .
        The problem occurred because after DB2 implicitly dropped
        at COMMIT those DGTTs defined as ON COMMIT DROP TABLE, DB2 did
        not check if other DGTTs remained for that DBAT; so therefore,
        DB2 did not mark the DBAT as 'cannot go inactive at COMMIT'.
                                                                       .
        This problem only occurs when using DGTTs defined as ON COMMIT
        DROP TABLE while other DGTTs created from the workload do NOT
        use ON COMMIT DROP TABLE -- basically, only if there is a 'mix'
        of the two types. So to circumvent the problem and those DBAT
        conditions, if possible, make all the DGTTs be the same type
        even across different applications by doing one of
        the following:
        (1) remove the ON COMMIT DROP TABLE attribute and, instead,
1           explicitly do SQL DROP TABLE for the DGTTs before COMMIT, OR
        (2) make all the DGTTs created by all of the applications /
            workloads run on this DBAT use ON COMMIT DROP TABLE
                                                                       .
        This problem with ON COMMIT DROP TABLE only occurs for DB2 9/10
        for z/OS, not for DB2 11.
                                                                       .
        A second problem discovered is when an SQL ROLLBACK occurs for
        a DBAT that still has remaining DGTTs 'after' the DB2 ROLLBACK
        process is done, DB2 did not mark the DBAT as 'cannot go
        inactive at ROLLBACK'.  Thus, the same previously described DBAT
        conditions and symptoms could occur following an SQL ROLLBACK
        for the DB2 thread. However, this second problem specific to
        ROLLBACK can occur regardless of usage of ON COMMIT DROP TABLE,
        and applies to DB2 9/10/11 for z/OS.
        For DB2 9/10, DB2 COMMIT processing was corrected to prevent
        a DBAT going inactive and being pooled if DGTTs still remain
        for this DB2 thread after DB2 implicitly drops the DGTTs defined
        as ON COMMIT DROP TABLE.
                                                                       .
        For DB2 9/10/11, DB2 ROLLBACK processing was corrected to
        prevent a DBAT going inactive and being pooled if DGTTs still
        remain 'after' DB2 ROLLBACK processing.
                                                                       .
        Note that even after applying this PTF, if you did not make
        changes to your remote application to ensure *all* DGTTs are
        dropped before a COMMIT or ROLLBACK point, you will still
        validly encounter the reported DBAT conditions/symptoms/messages
        but they will occur for the DBAT user who actually created/
        defined the DGTTs rather than for a later user of the DBAT.
                                                                       .
        Additional search keywords: DB2DDF DB2INACTIVE SQLDGTT
                                    RC00D3003B

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM91165
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXECW   PM91165
       DSNXECWA  PM91165
       DSNXMIT2  PM91165

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM91165   DSNXECW  DSNXECWA DSNXMIT2

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXECW
       DSNXECWA
       DSNXMIT2

      LISTEND
1UK96651 COVER LETTER END


 UK96652 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM94052 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users                    *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C4 PIC4 in DSNKINSL+4A1A or other *
        *                      modules                                 *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The abend occurs after an error is returned from DB2's buffer
        manager component because the code falls through to code that
        was only intended to be executed during recover.  This code uses
        a pointer that is only initialized for the recover path.
        Accessing the uninitialized pointer caused the abend.  Since
        this code occurs in a common macro used by DB2's data manager
        and index manager components, the abend may also occur in those
        modules that use this macro.
        The common macro is fixed to prevent the code from falling
        through to code that should not be executed when not in recover.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM94052
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNIB     PM94052
       DSNIBHUN  PM94052
       DSNICLAP  PM94052
       DSNICLCU  PM94052
       DSNICLPM  PM94052
       DSNICPOS  PM94052
       DSNICREL  PM94052
       DSNICSEC  PM94052
       DSNICUB   PM94052
       DSNICUMW  PM94052
       DSNICUR   PM94052
       DSNIDCML  PM94052
       DSNIDILS  PM94052
       DSNIDLDS  PM94052
       DSNIDLDU  PM94052
       DSNIDLEO  PM94052
       DSNIDNEX  PM94052
       DSNIELOD  PM94052
       DSNIESEN  PM94052
       DSNIFDPO  PM94052
       DSNIFFRE  PM94052
       DSNIFNP   PM94052
       DSNIFXRE  PM94052
       DSNIHDUP  PM94052
       DSNIHLOD  PM94052
1      DSNIHSET  PM94052
       DSNIKDEF  PM94052
       DSNILAST  PM94052
       DSNILGBW  PM94052
       DSNILPG   PM94052
       DSNIMNEX  PM94052
       DSNIMSAR  PM94052
       DSNIMSBR  PM94052
       DSNIMSCU  PM94052
       DSNIMSRI  PM94052
       DSNIMS1W  PM94052
       DSNINXPG  PM94052
       DSNINXPT  PM94052
       DSNINXTP  PM94052
       DSNIOST2  PM94052
       DSNIOW    PM94052
       DSNIOWRE  PM94052
       DSNIPBAC  PM94052
       DSNIPCFL  PM94052
       DSNIPCHC  PM94052
       DSNIPFLC  PM94052
       DSNIPGSP  PM94052
       DSNIPOCC  PM94052
       DSNIPOCH  PM94052
       DSNIPOCI  PM94052
       DSNIPOCR  PM94052
       DSNIPOSP  PM94052
       DSNIPOSS  PM94052
       DSNIPREP  PM94052
       DSNIPTYM  PM94052
       DSNIRCLS  PM94052
       DSNIRDCU  PM94052
       DSNIRECU  PM94052
       DSNIRELD  PM94052
       DSNKBIDP  PM94052
       DSNKBULD  PM94052
       DSNKCKOP  PM94052
       DSNKDLE   PM94052
       DSNKELD2  PM94052
       DSNKINSL  PM94052
       DSNKINSN  PM94052
       DSNKINUR  PM94052
       DSNKISPL  PM94052
       DSNKISPN  PM94052
       DSNKLLFS  PM94052
       DSNKLNLI  PM94052
       DSNKLNLS  PM94052
       DSNKLNPG  PM94052
       DSNKLTCH  PM94052
       DSNKLVLC  PM94052
       DSNKMDEL  PM94052
       DSNKSALO  PM94052
       DSNKSDEA  PM94052
       DSNKUREP  PM94052
       DSNOLADS  PM94052
       DSNOLDEL  PM94052
1
      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM94052   DSNIB    DSNIBHUN DSNICLAP DSNICLCU DSNICLPM DSNICPOS
                 DSNICREL DSNICSEC DSNICUB  DSNICUMW DSNICUR  DSNIDCML
                 DSNIDILS DSNIDLDS DSNIDLDU DSNIDLEO DSNIDNEX DSNIELOD
                 DSNIESEN DSNIFDPO DSNIFFRE DSNIFNP  DSNIFXRE DSNIHDUP
                 DSNIHLOD DSNIHSET DSNIKDEF DSNILAST DSNILGBW DSNILPG
                 DSNIMNEX DSNIMSAR DSNIMSBR DSNIMSCU DSNIMSRI DSNIMS1W
                 DSNINXPG DSNINXPT DSNINXTP DSNIOST2 DSNIOW   DSNIOWRE
                 DSNIPBAC DSNIPCFL DSNIPCHC DSNIPFLC DSNIPGSP DSNIPOCC
                 DSNIPOCH DSNIPOCI DSNIPOCR DSNIPOSP DSNIPOSS DSNIPREP
                 DSNIPTYM DSNIRCLS DSNIRDCU DSNIRECU DSNIRELD DSNKBIDP
                 DSNKBULD DSNKCKOP DSNKDLE  DSNKELD2 DSNKINSL DSNKINSN
                 DSNKINUR DSNKISPL DSNKISPN DSNKLLFS DSNKLNLI DSNKLNLS
                 DSNKLNPG DSNKLTCH DSNKLVLC DSNKMDEL DSNKSALO DSNKSDEA
                 DSNKUREP DSNOLADS DSNOLDEL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIB
       DSNIBHUN
       DSNICLAP
       DSNICLCU
       DSNICLPM
       DSNICPOS
       DSNICREL
       DSNICSEC
       DSNICUB
       DSNICUMW
       DSNICUR
       DSNIDCML
       DSNIDILS
       DSNIDLDS
       DSNIDLDU
       DSNIDLEO
       DSNIDNEX
       DSNIELOD
       DSNIESEN
       DSNIFDPO
       DSNIFFRE
       DSNIFNP
       DSNIFXRE
       DSNIHDUP
       DSNIHLOD
       DSNIHSET
       DSNIKDEF
       DSNILAST
       DSNILGBW
       DSNILPG
       DSNIMNEX
       DSNIMSAR
       DSNIMSBR
       DSNIMSCU
       DSNIMSRI
       DSNIMS1W
1      DSNINXPG
       DSNINXPT
       DSNINXTP
       DSNIOST2
       DSNIOW
       DSNIOWRE
       DSNIPBAC
       DSNIPCFL
       DSNIPCHC
       DSNIPFLC
       DSNIPGSP
       DSNIPOCC
       DSNIPOCH
       DSNIPOCI
       DSNIPOCR
       DSNIPOSP
       DSNIPOSS
       DSNIPREP
       DSNIPTYM
       DSNIRCLS
       DSNIRDCU
       DSNIRECU
       DSNIRELD
       DSNKBIDP
       DSNKBULD
       DSNKCKOP
       DSNKDLE
       DSNKELD2
       DSNKINSL
       DSNKINSN
       DSNKINUR
       DSNKISPL
       DSNKISPN
       DSNKLLFS
       DSNKLNLI
       DSNKLNLS
       DSNKLNPG
       DSNKLTCH
       DSNKLVLC
       DSNKMDEL
       DSNKSALO
       DSNKSDEA
       DSNKUREP
       DSNOLADS
       DSNOLDEL

      LISTEND
 UK96652 COVER LETTER END


 UK96657 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86700 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of       *
        *                 native SQL routines with XML or LOB type     *
1       *                 input parameters under DEBUG mode.           *
        ****************************************************************
        * PROBLEM DESCRIPTION: An ABEND04E rc00E70005 can occur at     *
        *                      location DSNXRGPL M110 or at location   *
        *                      DSNNXML.DSNNAINP M140 when running a    *
        *                      native SQL routine that contains an     *
        *                      XML or LOB input parameter when in      *
        *                      DEBUG mode.                             *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An ABEND04E rc00E70005 can occur at location DSNXRGPL M110 when
        running a native SQL UDF (User Defined Function) that contains
        an XML input parameter when in DEBUG mode.

        The above mentioned intentional abend occurs because DB2 does
        not support XML parameters for native SQL UDFs while running
        under DEBUG mode.

        Here is an example of such a function:

          CREATE FUNCTION FUNCTION1 (var1 XML  )
               RETURNS  XML
               VERSION V1
               DETERMINISTIC
               NO EXTERNAL ACTION
               CONTAINS SQL
               WLM ENVIRONMENT FOR DEBUG MODE WLMENV1
               ALLOW DEBUG MODE

            BEGIN
                  RETURN var1;
            END

        When this function is deployed to run in DEBUG mode, the above
        mentioned intentional abend can occur.

        Another error scenario is when a LOB or XML type input parameter
        has been updated inside the SQL routine with a different length.
        This can result in an abend at location DSNNXML.DSNNAINP M140 or
        in certain cases, an incorrect result could be returned instead.
        The code in DB2 has been modified to support XML type parameters
        for native SQL routines under DEBUG mode to prevent the abend
        from being issued.

        Additional Keywords: SQLNATIVESQLPL SQLUDF SQLXML SQLSP
                             SQLSTOREDPROC SQLPROCEDURE INCORROUT
                             SQLINCORR SQLINCORROUT
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM86700
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXRGPL  PM86700
1      DSNXRPL9  PM86700
       DSNXRPPL  PM86700
       DSNXRSPL  PM86700

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM86700   DSNXRGPL DSNXRPL9 DSNXRPPL DSNXRSPL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXRGPL
       DSNXRPL9
       DSNXRPPL
       DSNXRSPL

      LISTEND
 UK96657 COVER LETTER END


 UK96662 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM92126 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS      *
        *                 users of Large Objects (LOBs).               *
        ****************************************************************
        * PROBLEM DESCRIPTION: An ABEND04E RC00C900DA at location      *
        *                      DSNOCHLO +1374 or at DSNOCHLO +14DE can *
        *                      occur when an application attempted to  *
        *                      hold an application LOB locator.        *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An ABEND04E RC00C900DA can occur at location DSNOCHLO +1374
        (OFFSET1374) or at DSNOCHLO +14DE (OFFSET14DE) when an
        application attempts to hold an application LOB locator when the
        number of concurrently held application LOB locators does not
        exceed the maximum limit.

        The reason the abend occurs is that DB2 failed to correctly
        adjust an internal counter when an application freed a held LOB
        locator.  This counter keeps track of the total number of active
        held application locators for each active thread.  Subsequently,
        when the application attempts to hold another LOB locator, it
        then exceeds the allowable limit, thus resulting in the
        intentional abend mentioned above.  Instead, the operation to
        hold the application LOB locator should succeed.

        The following example (application code snippet) helps to
        illustrate a failing scenario.

          DO IX = 1 TO 65535;   !Use locator limit
            EXEC SQL SELECT COLCLOB INTO :HVCLOBL1 FROM MYTB WHERE
            COLINT = 1;

            EXEC SQL HOLD LOCATOR :HVCLOBL1;
1
            EXEC SQL FREE LOCATOR :HVCLOBL1;
          END;

          EXEC SQL SELECT COLCLOB INTO :HVCLOBL1 FROM MYTB WHERE
           COLINT = 1;

          EXEC SQL HOLD LOCATOR :HVCLOBL1;

        The code in DB2 is modified to correctly decrement the internal
        counter regarding LOB locators to avoid the abend.

        Additional Keywords: SQLLOB
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM92126
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNOFRLC  PM92126

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM92126   DSNOFRLC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNOFRLC

      LISTEND
 UK96662 COVER LETTER END


 UK96670 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM91213 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS, DB2 10 for z/OS and DB2  *
        *                 11 for z/OS users of UNLOAD utility with     *
        *                 FLOAT IEEE                                   *
        ****************************************************************
        * PROBLEM DESCRIPTION: UNLOAD FLOAT IEEE without field         *
        *                      specification unloaded data in HFP      *
        *                      format instead of BFP format            *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        UNLOAD FLOAT IEEE was incorrectly unloading floating point
        data in hexadecimal floating point (HFP) format instead of
        binary floating point (BFP) format when a field specification
        was not used. The UNLOAD without a field specification was not
        taking into account that the FLOAT IEEE option was being used,
        thus did not perform any data conversions.
        UNLOAD has been changed to unload data using the correct format
        for the no field-specification cases when using FLOAT IEEE
1       option.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM91213
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUUUCA  PM91213

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM91213   DSNUUUCA

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUUUCA

      LISTEND
 UK96670 COVER LETTER END


 UK96681 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88609 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of the DB2         *
        *                 Dynamic Statement Cache and dynamic          *
        *                 MERGE SQL with prepare attribute             *
        *                 CONCENTRATE STATEMENTS WITH LITERALS         *
        ****************************************************************
        * PROBLEM DESCRIPTION: SQLCODE -433 may be issued incorrectly  *
        *                      during execution of a cached MERGE      *
        *                      dynamic SQL statement with the          *
        *                      prepare attribute CONCENTRATE           *
        *                      STATEMENTS WITH LITERALS                *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The reported SQLCODE -433 occurred during execution of
        a MERGE dynamic SQL statement when Dynamic Statement
        Caching (DSC) is active and all of the following conditions
        were true:

        1) the dynamic MERGE SQL statement was prepared with the
           attribute CONCENTRATE STATEMENT WITH LITERALS, and the
           literal string constants that are specified in the source
           table VALUES clause are qualified for literal constant
           reuse.

        2) The new MERGE dynamic statement contains string literal
            constants that are specified in the VALUES clause of the
            source table. The length of at least one literal in
            this new MERGE statement is greater than the corresponding
            literal in the existing cached MERGE statement

1
        3) during PREPARE the MERGE dynamic statement successfully
            cache-matched with the existing cached MERGE statement
            that contains literal string constants that are specified
            in the VALUES for the source table even though the length
            of the literal string constants are different (this is
            the cache statement sharing behavior when using attribute
            CONCENTRATE STATEMENTS WITH LITERALS)


        For Example,
          MERGE INTO T1  T
           USING (VALUES ('a')) AS S(C1)
           ON T.C1 = S.C1
           WHEN MATCHED THEN
            UPDATE SET T.C1 = S.C1
           WHEN NOT MATCHED THEN
            INSERT (C1) VALUES (S.C1)
          NOT ATOMIC CONTINUE ON SQLEXCEPTION;

          MERGE INTO T1  T
            USING (VALUES ('ab')) AS S(C1)
            ON T.C1 = S.C1
            WHEN MATCHED THEN
             UPDATE SET T.C1 = S.C1
           WHEN NOT MATCHED THEN
             INSERT (C1) VALUES (S.C1)
          NOT ATOMIC CONTINUE ON SQLEXCEPTION;

        The second MERGE statement may receive an SQLCODE -433
        because DB2 is trying to share the buffer which was allocated
        for constant 'a' with constant 'ab'.
        DB2 Dynamic Statement Caching CONCENTRATE STATEMENTS WITH
        LITERALS behavior for MERGE SQL statement has been changed to
        only allow a successful cache match between MERGE statements
        where the string literal constants that are specified in
        the source table value clause are an exact type and length match
        between the two MERGE statement.
        This allows DB2 to correctly prepare the subsequent MERGE.

        Additional search keywords: SQLCODE433 SQLDYNSTMTCACHE SQLMERGE

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88609
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOP0   PM88609

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88609   DSNXOP0

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

1     MODULES
       DSNXOP0

      LISTEND
 UK96681 COVER LETTER END


 UK96687 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90890 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users                    *
        ****************************************************************
        * PROBLEM DESCRIPTION: Tracking internal CT Data Base Block    *
        *                      creation.                               *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        This is a serviceability apar to track the internal
        CT Data Base Block creation.
        Add code in DB2 to track CT Data Base block creation.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM90890
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNIBCTD  PM90890
       DSNICUBC  PM90890
       DSNIFDBD  PM90890
       DSNIFOD   PM90890
       DSNIFOI   PM90890
       DSNIFPSC  PM90890
       DSNIHPGM  PM90890

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90890   DSNIBCTD DSNICUBC DSNIFDBD DSNIFOD  DSNIFOI  DSNIFPSC
                 DSNIHPGM

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIBCTD
       DSNICUBC
       DSNIFDBD
       DSNIFOD
       DSNIFOI
       DSNIFPSC
       DSNIHPGM

      LISTEND
 UK96687 COVER LETTER END


 UK96691 COVER LETTER START
1   PROBLEM DESCRIPTION(S):
      PM88829 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9, 10 and 11 for z/OS users of XML   *
        *                 publishing function.                         *
        ****************************************************************
        * PROBLEM DESCRIPTION: An ABEND0C4 at DSNXGRDS DSNXXAGG +1B94  *
        *                      might occur while running XML           *
        *                      publishing functions.                   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An ABEND0C4 at DSNXGRDS DSNXXAGG +1B94 might occur while running
        XML publishing functions.

        The XML publishing functions did not handle the error return
        code properly. Such as when the memory allocation reaches the
        user or system limit, an error return code will be returned by
        the memory allocation function. The XML publishing function did
        not handle this error return code and continue. This causes DB2
        to ABEND when the invalid data is used in the subsequent
        processing.
        DB2 is modified to handle the error return code properly, so
        the SQL message will be issued in stead of ABEND. For example,
        in the case of memory allocation reaches the limit, SQLCODE -904
        should be issued, instead of ABEND.

        Additional keywords: SQLXML XMLALL
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88829
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXXAGG  PM88829
       DSNXXGEN  PM88829

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88829   DSNXXAGG DSNXXGEN

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXXAGG
       DSNXXGEN

      LISTEND
 UK96691 COVER LETTER END


 UK96695 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM93121 -
        ****************************************************************
        * USERS AFFECTED: All DB2 11 for z/OS users of BIND QUERY or   *
1       *                 selectivity overrides, and                   *
        *                 all DB2 10 for z/OS and DB2 11 for z/OS      *
        *                 users of internal serviceability features.   *
        ****************************************************************
        * PROBLEM DESCRIPTION: For DB2 11 for z/OS users, the          *
        *                      following symptom may occur when using  *
        *                      BIND QUERY:                             *
        *                                                              *
        *                      ABEND0C4 RC00000004 in DSNXOBNQ +074A   *
        *                                                              *
        *                      For DB2 11 for z/OS users, the          *
        *                      following symptom may occur when using  *
        *                      selectivity overrides:                  *
        *                                                              *
        *                      SQLCODE +395 reason code '43'           *
        *                                                              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        For DB2 11 for z/OS users, the following symptom may occur when
        using BIND QUERY:

          ABEND0C4 RC00000004 in DSNXOBNQ +074A

        For DB2 11 for z/OS users, the following symptom may occur when
        using selectivity overrides:

          SQLCODE +395 reason code '43'

        This APAR also fixes problems that can occur on DB2 10 for z/OS
        and DB2 11 for z/OS when using internal serviceability features
        in DB2 that aid in debugging query optimization issues.

        The above problems were caused by program error.

        Additional keywords:
        ABEND0C4 RC00000004 OFFSET074A SQLCODE395 SQLSTORAGE
        DBUGFLAG

        DB2 code has been changed to fix the problems and avoid issuing
        the abend. Also, the SQLCODE will not be issued incorrectly.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM93121
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOD3   PM93121

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM93121   DSNXOD3

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
1      DSNXOD3

      LISTEND
 UK96695 COVER LETTER END


 UK96725 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM91600 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS users of incremental        *
        *                 rebind                                       *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C4 RC00000004 in DSNXERB          *
        *                      OFFSET2812 encountered during           *
        *                      incremental rebind                      *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        During incremental rebind, a lock request on SYSIBM.SYSPACKSTMT
        encountered a timeout, causing DB2 logic to take the error path.
        In this error path, DB2 referenced an unavailable control block.
        As a result, the ABEND0C4 RC00000004 in DSNXERB OFFSET2812 was
        encountered.
        DB2 was modified to correctly check for the addressability of
        the control block in question before accessing it.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM91600
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXERB   PM91600

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM91600   DSNXERB

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXERB

      LISTEND
 UK96725 COVER LETTER END


 UK96734 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM92535 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS RRS users.                  *
        ****************************************************************
        * PROBLEM DESCRIPTION: URs for RRS Resource Managers processed *
        *                      inconsistently when DB2 is cancelled    *
        *                      between phase one and phase 2 commit    *
1       *                      for a RRS UR.  In this case of an       *
        *                      MQBroker transaction the MQSeries UR    *
        *                      was committed but the DB2 UR was        *
        *                      aborted.                                *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        UR processing may be inconsistent when z/OS RRS can call
        MQSeries to process phase 2 commit, but DB2 is cancelled before
        it can process the phase 2 commit.  If Z/OS RRS recovery
        receives a percolated 0004F000 from DB2 termination, RRS
        completes its UR processing.  During DB2 restart and resynch
        with z/OS RRS, DB2 follows presume abort protocol and aborts the
        DB2 UR associated with the RRS UR.
        Module DSN3RRSX has been updated to correctly inform z/OS RRS
        about the status of the DB2 UR associated with the z/OS RRS UR
        which is being committed.
    COMPONENT:  5740-XYR01-HIZAA10
    APARS FIXED: PM92535
    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

        IBM recommends that you install DB2 APAR PM59756
        PTFs UK77559, UK77560 or UK77561 on all
        DB2 for z/OS DB2 subsystems to fix HIPER APAR
        PM59756 before installing this RRSAF ERLY code PTF
        or other DB2 PTFs for RRSAF.  PM59756 fixes a base
        DB2 V10 problem.
      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

        IBM recommends that you install DB2 PTF UK77559 to fix HIPER
        APAR PM59756 before installing this PTF or other DB2 PTFs for
        RRSAF.  PM59756 fixes a base DB2 V10 problem.
      ACTION:
        This PTF requires either an ERLY code refresh or a re-IPL of
        zOS.
1
        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 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 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:
        In order for this PTF to be fully effective, an IPL with CLPA or
        REFRESH DB2,EARLY is required.  The DB2 member should be
        stopped before issuing the REFRESH DB2, EARLY command.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSN3RRSX  PM92535

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM92535   DSN3RRSX

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSN3RRSX

      LISTEND
1UK96734 COVER LETTER END


 UK96744 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM87044 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for zOS users of the CURRENT         *
        *                 OPTIMIZATION HINT special register           *
        *                 for remote applications                      *
        ****************************************************************
        * PROBLEM DESCRIPTION: The CURRENT OPTIMIZATION HINT           *
        *                      special register is set incorrectly     *
        *                      when using implicit DRDA or the JCC     *
        *                      properties.                             *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The setting of the CURRENT OPTIMIZATION HINT special register
        through implicit DRDA or through the JCC API does not set the
        special register correctly; garbage data is stored instead
        of the proper value.
        In addition, an error is not issued when a string longer than
        128 bytes is used to set CURRENT OPTIMIZATION HINT special
        register through an implicit DRDA connection or through the
        JCC API.
        DB2 is modified to set the CURRENT OPTIMIZATION HINT special
        register correctly.  For strings longer than 128 bytes, DB2
        will now issue sqlcode -725.

        Additional Keywords:
        SQLSPECIALREG
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM87044
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        <++HOLD text for pm87044>
        BEFORE APPLYING THIS PTF, SETTING THE CURRENT OPTIMIZATION HINT
        SPECIAL REGISTER FROM A JCC APPLICATION USING THE PROPERTIES API
        WITH AN INVALID STRING LENGTH > 128 BYTES RETURNED
        SQLCODE 0.

        AFTER APPLYING THIS PTF, DB2 WILL NOW CORRECTLY INDICATE THIS
        IS AN INVALID STRING BECAUSE IT IS LONGER THAN THE ALLOWED
        LENGTH.  DB2 WILL NOW ISSUE SQLCODE -725 FOR THIS SITUATION.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXESSR  PM87044
       DSNXRSPG  PM87044
       DSNXRSQO  PM87044

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM87044   DSNXESSR DSNXRSPG DSNXRSQO

1     THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXESSR
       DSNXRSPG
       DSNXRSQO

      LISTEND
 UK96744 COVER LETTER END


 UK96752 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM92790 -
        ****************************************************************
        * USERS AFFECTED: All DB2 V9, 10 or 11 for z/OS users of an    *
        *                 SQL statement that contains a table          *
        *                 expression or view with SET operators,       *
        *                 multiple CCSIDs and Date or Timestamp data.  *
        ****************************************************************
        * PROBLEM DESCRIPTION: 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.                  *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An example is shown below:

        CREATE TABLE T1 (
          C1 CHAR(40) FOR SBCS DATA NOT NULL,
          C2 CHAR(40) FOR SBCS DATA,
          C3 DATE
        ) CCSID UNICODE;

        CREATE TABLE T2 (
          C1 CHAR(4) NOT NULL,
          C2 CHAR(4)
        ) CCSID EBCDIC;

        COMMIT;

        INSERT INTO T1 VALUES('2013-02-02', '2013-03-03', '2013-01-01');
        INSERT INTO T1 VALUES('2013-02-02', '2013-03-03', '2013-01-01');
        INSERT INTO T2 VALUES('C11', 'C21');
        INSERT INTO T2 VALUES('C12', 'C22');
1       COMMIT;

        SELECT * FROM
        (
          SELECT '2013-06-06'
          FROM T2
          UNION
          SELECT T1.C3
          FROM T1
          UNION
          SELECT COALESCE(T1.C1, T1.C2)
          FROM T1
        ) TX(C1)
        ;

        DB2 did not correctly process the aforementioned SQL statements,
        which caused the ABEND or incorrect SQLCODE -180.
        DB2 has been modified to correctly process the aforementioned
        SQL statement, so there will be no ABEND or incorrect SQLCODE
        -180.

        Additional keywords: SQLTABLEEXPR SQLUNION SQLUNIONALL
                             SQLINTERSECT SQLINTERSECTALL SQLEXCEPT
                             SQLEXCEPTALL SQLCCSID SQLCODE180 SQLTIME
                             SQLDATE
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM92790
    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
        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.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOCT   PM92790

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1      PM92790   DSNXOCT

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOCT

      LISTEND
 UK96752 COVER LETTER END


 UK96787 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM94149 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users *
        *                 of the IFCID 96 sort trace record when       *
        *                 either the program or package name exceeds   *
        *                 18 bytes in length.                          *
        ****************************************************************
        * PROBLEM DESCRIPTION: An ABEND0C4 can occur in the Omegamon   *
        *                      tool (possibly OMPE520) when it tries   *
        *                      to process an IFCID96 sort trace record *
        *                      when either the program name or package *
        *                      name is over 18 bytes in length.        *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An ABEND0C4 can occur in the Omegamon tool (possibly OMPE520)
        when it tries to process an IFCID96 SORT trace record when
        either the program name or package name exceeds 18 bytes in
        length.

        The IFCID96 SORT trace record builds the longer program and
        package names at the end of the entire trace record in an
        extension area.  But, when the trace record is cut, the
        extension area is not passed to the trace routine.  So, when the
        Omegamon tool looks for the longer name, it could be in some
        other storage which could cause an abend, contain invalid data,
        or cause some other kind of error.
        DB2 has been modified to correct the IFCID96 trace record for
        longer program and package names.

        Additional Keywords: IFCID96 OMEGAMON DB2SORT
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM94149
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXSFTP  PM94149
       DSNXSORI  PM94149

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM94149   DSNXSFTP DSNXSORI
1
      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXSFTP
       DSNXSORI

      LISTEND
 UK96787 COVER LETTER END


 UK96800 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM92742 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS, DB2 10 for z/OS and      *
        *                 DB2 11 for z/OS users of the RUNSTATS        *
        *                 utility.                                     *
        ****************************************************************
        * PROBLEM DESCRIPTION: AVGROWLEN in SYSIBM.SYSTABLES should    *
        *                      not include the two byte ID map as      *
        *                      part of the AVGROWLEN.                  *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        The AVGROWLEN in SYSTABLES set by the RUNSTATS utility includes
        the length of the two byte ID map entry so that it will equal
        the RECLENGTH statistic also in SYSIBM.SYSTABLES.  This is
        incorrect and the AVGROWLEN should only include the average
        length of the data row.
        A similar problem can occur on SYSTABLES.AVGROWLEN value
        gathered inline by the LOAD and REORG utilities.
        Code has been modified to no longer include the two byte
        length of the ID map in the RUNSTATS AVGROWLEN statistic in
        SYSIBM.SYSTABLES.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM92742
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        The PTF for APAR PM92742 has modified the SYSTABLES.AVGROWLEN
        statistic collected by the RUNSTATS utility.  The AVGROWLEN will
        no longer include the length of the ID map entry and therefore
        may no longer be equal to the RECLENGTH statistic in the
        same catalog table, SYSTABLES.  This change will make the
        AVGROWLEN consistent with the AVGROWLEN catalog statistics
        in SYSTABLESPACE and SYSTABLEPART gathered by RUNSTATS.
        A similar problem can occur on SYSTABLES.AVGROWLEN value
        gathered inline by the LOAD and REORG utilities.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUSUTB  PM92742

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM92742   DSNUSUTB
1
      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUSUTB

      LISTEND
 UK96800 COVER LETTER END


 UK96807 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM94148 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users that utilize dump  *
        *                 processing.                                  *
        ****************************************************************
        * PROBLEM DESCRIPTION: An abend can occur in module DSNXDMPS   *
        *                      if the values derived from the general  *
        *                      registers for various control blocks    *
        *                      have an invalid address.                *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An abend can occur in module DSNXDMPS if the values derived from
        the general registers for various control blocks have an invalid
        address.

        The abend will not be seen by the user since it is encountered
        during dump processing for another issue which is the main
        concern.  However, this abend could cause certain control blocks
        to not be dumped asynchronously or lead to some information not
        being dumped properly for later/proper diagnosis.  Sometimes
        this data may still be dumped synchronously and be used for
        further problem diagnosis if the system hasn't cleared the data
        yet.

        The dump processing routine was always checking the 31-bit
        register to be used for dumping certain control blocks.  But,
        this value will be invalid if the module that failed was running
        in AMODE(64).  Therefore, dump processing needs to recognize
        when to use a 64-bit register for dumping a given control block.
        DB2 has been modified to check the environment of the failing
        module so that it will use the proper 31-bit or 64-bit general
        register to address or retrieve the proper control block
        information.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM94148
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXDMPS  PM94148

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1      PM94148   DSNXDMPS

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXDMPS

      LISTEND
 UK96807 COVER LETTER END


 UK96810 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88251 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS users.                      *
        ****************************************************************
        * PROBLEM DESCRIPTION: AE PM64388 fix completion.              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        AE PM64388 fix completion.
        AE PM64388 fix completion.
    COMPONENT:  5740-XYR01-HIZAA10
    APARS FIXED: PM88251
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR01 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        This PTF updates the ERLY code. After you apply this fix,
        you must either re-IPL z/OS with CLPA, or issue the -REFRESH DB2
        command.

        The procedure for issuing the REFRESH command is:

        1. Issue -STOP DB2
        2. Issue MODIFY LLA,REFRESH
        3. Issue -REFRESH DB2,EARLY
      ACTION:
        This PTF updates the ERLY code. After you apply this fix,
        you must either re-IPL z/OS with CLPA, or issue the -REFRESH DB2
        command.

        The procedure for issuing the REFRESH command is:

        1. Issue -STOP DB2
        2. Issue MODIFY LLA,REFRESH
        3. Issue -REFRESH DB2,EARLY
      ACTION:
        This PTF updates the ERLY code. After you apply this fix,
        you must either re-IPL z/OS with CLPA, or issue the -REFRESH DB2
        command.

        The procedure for issuing the REFRESH command is:

        1. Issue -STOP DB2
1       2. Issue MODIFY LLA,REFRESH
        3. Issue -REFRESH DB2,EARLY
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSN3UR00  PM88251

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88251   DSN3UR00

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSN3UR00

      LISTEND
 UK96810 COVER LETTER END


 UK96816 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM94536 -
        ****************************************************************
        * USERS AFFECTED: Users of a DB2 for z/OS ODBC multi-context   *
        *                 applicaton.                                  *
        ****************************************************************
        * PROBLEM DESCRIPTION: An SQL call on an ODBC connection using *
        *                      MULTICONTEXT=2 may get an ABEND0C4 if   *
        *                      DSNARRS has been released via an MVS    *
        *                      DELETE, due to incorrect connection     *
        *                      processing.                             *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An SQL call on an ODBC connection using MULTICONTEXT=2 may get
        an ABEND0C4 if DSNARRS has been released via an MVS DELETE, due
        to incorrect connection processing.
        DB2 RRSAF Identify processing results in language interface
        module DSNRLI doing an MVS LOAD of the RRSAF attachment
        module DSNARRS.  RRSAF Terminate Identify processing results
        in module DSNRLI doing an MVS DELETE of DSNARRS.  However, in
        the the ODBC MULTICONTEXT=2 environment the DB2 connection may
        be shifted away from task (TCB or Task Control Block) that
        created the DB2 connection.  MVS LOAD / DELETE processing
        manages the load module as a TCB related resource, so if the
        TCB goes through MVS termination processing, the DSNARRS
        load count may be decremented, or the module DSNARRS may be
        removed from virtual storage if the load count is decremented
        to zero.  If another TCB uses the DB2 connection when DSNARRS
        has been deleted, an ABEND0C4 may occur on the call to
        DSNARRS.
        If the TCB that created the DB2 connection also terminates the
        DB2 connection before the TCB itself terminates, then the MVS
        LOAD / DELETE processing and the DB2 connection processing
        will be synchronized.
        If an ODBC connection using MULTICONTEXT=2 is initiated, ODBC
        may signal DB2 and DSNRLI will then avoid doing an MVS DELETE
1       of DSNARRS.
        Module DSNRLI has been updated to avoid deleting DSNARRS when
        it is signaled by ODBC to do so.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM94536
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNRLI    PM94536

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM94536   DSNRLI

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNRLI

      LISTEND
 UK96816 COVER LETTER END


 UK96817 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90421 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS      *
        *                 utility users of LOAD with CCSID conversion  *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABENDS0C4 RC4 at CUN4MU2U +x'0120'      *
        *                      occurs during CCSID conversion          *
        *                      processing for a LOB column during a    *
        *                      LOAD utility                            *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        LOAD of a UNICODE table containing a LOB column with EBCDIC data
        abends with ABEND0C4 at CUN4MU2U OFFSET0120 during CCSID
        conversion.  The abend occurred because the buffer passed for
        the conversion of the LOB data was short 4 bytes and the next
        page of storage was allocated but in a different storage key.
        LOAD of a UNICODE table processing has been changed to acquire a
        larger buffer for LOB translation to UNICODE.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM90421
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNURNFL  PM90421
       DSNURUFL  PM90421

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1      PM90421   DSNURNFL DSNURUFL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNURNFL
       DSNURUFL

      LISTEND
 UK96817 COVER LETTER END


 UK96824 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90182 -
        ****************************************************************
        * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
        *                 Specifically those where remote systems use  *
        *                 RACF PassTickets to access DB2 for z/OS, as  *
        *                 a server, via TCP/IP.                        *
        ****************************************************************
        * PROBLEM DESCRIPTION: User incorrectly authenticated and      *
        *                      allowed access to a DB2 for z/OS        *
        *                      (server) system if PassTickets are      *
        *                      configured as non replayable.           *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When DB2 receives a PassTicket from a remote requester system,
        DB2 invokes RACF to authenticate the userID and PassTicket.  If
        a requester system then immediately tries to access DB2 with
        the same PassTicket, the remote connection is successfully
        authenticated even though the validity of the PassTicket should
        have expired after its initial use.
        The problem occurs because DB2 utilizes a technique of caching
        authentication credentials.  These cached credentials remain
        for three minutes thereby improving performance by avoiding
        calls to RACF when/if the same credentials are encountered again
        during that three minute period.  However, DB2 failed to
        consider that PassTickets may be defined as non replayable in
        which case a user can be incorrectly authenticated by a non
        replayable PassTicket that has been cached.

        DB2 has been changed to bypass its caching technique for
        PassTickets when NO REPLAY PROTECTION is not specified.
        Documentation changes are also necessary to describe how to
        influence the DB2 caching of PassTickets.  This information
        will be available in the Information Management Software for
        z/OS Solutions Information Center at a later date.
        *****
        When receiving RACF PassTickets over TCP/IP communications
        from a DB2 for z/OS requester, the following RACF actions must
        be taken for global authentication cache not to be used for
        PassTickets when "NO REPLAY PROTECTION" is not specified in
        the PassTicket profile.

1       - A RACF PTKTDATA resource profile must be created at the
          server system or sysplex using the following naming rules:

          RDEFINE PTKTDATA IRRPTAUTH.applname.userid or
          RDEFINE PTKTDATA IRRPTAUTH.applname.*

          Where applname is either the generic LU name or IPNAME
          assigned to each member of a serving data sharing group
          or is the LUNAME or IPNAME assigned to the serving
          non-data sharing subsystem.

          Where userid is either an asterisk ("*") or a RACF userid
          that one wants to allow into the serving subsystem or
          member of a data sharing group.

        - Once the RACF profile has been defined, the PTKTDATA resource
          must be refreshed as follows:

          SETROPTS RACLIST(PTKTDATA) REFRESH

        - Once the PTKTDATA resource profiles have been refreshed and
          loaded, the userid assigned in the STDATA of the STARTED
          profile of the ssidDIST address space must be permitted to
          read this new profile as follows:

          PERMIT IRRPTAUTH.applanme.userid CLASS(PTKTDATA) -
            ID(dist_userid) ACCESS(READ) or
          PERMIT IRRPTAUTH.applname.* CLASS(PTKTDATA) -
            ID(dist_userid) ACCESS(READ)

          Where userid and dist_userid are not the same.

        The above actions do not need to be taken if one wants to take
        advantage of global authentication cache for PassTickets.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM90182
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DOCUMENTATION:
        ***Documentation for PM90182:

        See PM90182 APAR/PTF text for additional information.

        The following text describes the function that is provided
        by this APAR. This information will be available in the
        Information Management Software for z/OS Solutions
        Information Center at a later date.

        When receiving RACF PassTickets over TCP/IP communications
        from a DB2 for z/OS requester, the following RACF actions must
        be taken for global authentication cache not to be used for
        PassTickets when "NO REPLAY PROTECTION" is not specified in
        the PassTicket profile.

        - A RACF PTKTDATA resource profile must be created at the
1         server system or sysplex using the following naming rules:

          RDEFINE PTKTDATA IRRPTAUTH.applname.userid or
          RDEFINE PTKTDATA IRRPTAUTH.applname.*

          Where applname is either the generic LU name or IPNAME
          assigned to each member of a serving data sharing group
          or is the LUNAME or IPNAME assigned to the serving
          non-data sharing subsystem.

          Where userid is either an asterisk ("*") or a RACF userid
          that one wants to allow into the serving subsystem or
          member of a data sharing group.

        - Once the RACF profile has been defined, the PTKTDATA resource
          must be refreshed as follows:

          SETROPTS RACLIST(PTKTDATA) REFRESH

        - Once the PTKTDATA resource profiles have been refreshed and
          loaded, the userid assigned in the STDATA of the STARTED
          profile of the ssidDIST address space must be permitted to
          read this new profile as follows:

          PERMIT IRRPTAUTH.applanme.userid CLASS(PTKTDATA) -
            ID(dist_userid) ACCESS(READ) or
          PERMIT IRRPTAUTH.applname.* CLASS(PTKTDATA) -
            ID(dist_userid) ACCESS(READ)

          Where userid and dist_userid are not the same.

        The above actions do not need to be taken if one wants to take
        advantage of global authentication cache for PassTickets.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNLTMIN  PM90182
       DSN3AUCN  PM90182

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90182   DSNLTMIN DSN3AUCN

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNLTMIN
       DSN3AUCN

      LISTEND
 UK96824 COVER LETTER END


 UK96839 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89897 -
        ****************************************************************
        * USERS AFFECTED: All Users of the IBM Data                    *
1       *                 Server Driver for JDBC and SQLJ              *
        ****************************************************************
        * PROBLEM DESCRIPTION: IBM Data Sever Driver for JDBC and      *
        *                      SQLJ version 3.65.96 is provided by     *
        *                      this APAR ( JCCV36596 )                 *
        *                                                              *
        *                      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.65) *
        *                      of the IBM Data Server Driver for JDBC  *
        *                      and SQLJ providing an accumulation of   *
        *                      defect fixes and enhancements.          *
        *                                                              *
        *                      Individual items are documented in the  *
        *                      APAR summary section that follows.      *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        JCC sub-category keywords:
        JCCCOMMON, JCCT2ZOS, JCCT4, JCCT4XA, JCCSQLJ

        The following changes are delivered in this APAR:
        _______________________________________________________________
        Type-2 z/OS connectivity: Various minor improvements to
        make loading the driver and connection establishment less
        expensive in terms of CPU and memory.(RTC 30648)
        _______________________________________________________________
        Type-2 z/OS connectivity: SQLJ application encounters data
        corruption in a multithreaded environment. This happens when
        callableStatement is executed under WAS with statement
        caching enabled. This issue is fixed.(RTC 30234 )
        _______________________________________________________________
        Type-4 connectivity: When using client affinities with an
        affinityFailbackInterval value the driver does not fail back
        to the primary server, even though the server may have
        become available. This issue is fixed.(RTC 32630)
        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: PM89897
    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
1       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  PM89897
       DSNAQJBB  PM89897
       DSNAQJB1  PM89897
       DSNAQJB2  PM89897
       DSNAQJB3  PM89897
       DSNAQJB4  PM89897
       DSNAQJB5  PM89897
       DSNAQJB6  PM89897
       DSNAQJB7  PM89897
       DSNAQJB8  PM89897
       DSNAQJC1  PM89897
       DSNAQJC2  PM89897
       DSNAQJC3  PM89897
       DSNAQJC4  PM89897
       DSNAQJRM  PM89897
       DSNAQJS1  PM89897
       DSNAQJS2  PM89897
       DSNAQ3CA  PM89897
       DSNAQ3CC  PM89897
       DSNAQ3CE  PM89897
       DSNAQ3CF  PM89897
       DSNAQ3CM  PM89897
       DSNAQ3C0  PM89897
       DSNAQ3C1  PM89897
       DSNAQ3C2  PM89897
       DSNAQ3C3  PM89897
       DSNAQ3C4  PM89897
       DSNAQ3C5  PM89897
       DSNAQ3C6  PM89897
       DSNAQ3C7  PM89897
       DSNAQ3C8  PM89897
       DSNAQ3C9  PM89897
       DSNAQ3E1  PM89897
       DSNAQ6CC  PM89897
       DSNAQ6CE  PM89897
       DSNAQ6CF  PM89897
       DSNAQ6CM  PM89897
       DSNAQ6C0  PM89897
       DSNAQ6C1  PM89897
       DSNAQ6C2  PM89897
       DSNAQ6C3  PM89897
       DSNAQ6C4  PM89897
       DSNAQ6C5  PM89897
       DSNAQ6C6  PM89897
       DSNAQ6C7  PM89897
1      DSNAQ6C9  PM89897

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89897   DSNAQJBA DSNAQJBB DSNAQJB1 DSNAQJB2 DSNAQJB3 DSNAQJB4
                 DSNAQJB5 DSNAQJB6 DSNAQJB7 DSNAQJB8 DSNAQJC1 DSNAQJC2
                 DSNAQJC3 DSNAQJC4 DSNAQJRM DSNAQJS1 DSNAQJS2 DSNAQ3CA
                 DSNAQ3CC DSNAQ3CE DSNAQ3CF DSNAQ3CM DSNAQ3C0 DSNAQ3C1
                 DSNAQ3C2 DSNAQ3C3 DSNAQ3C4 DSNAQ3C5 DSNAQ3C6 DSNAQ3C7
                 DSNAQ3C8 DSNAQ3C9 DSNAQ3E1 DSNAQ6CC DSNAQ6CE DSNAQ6CF
                 DSNAQ6CM DSNAQ6C0 DSNAQ6C1 DSNAQ6C2 DSNAQ6C3 DSNAQ6C4
                 DSNAQ6C5 DSNAQ6C6 DSNAQ6C7 DSNAQ6C9

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNAQ3CA
       DSNAQ3CC
       DSNAQ3CE
       DSNAQ3CF
       DSNAQ3CM
       DSNAQ3C0
       DSNAQ3C1
       DSNAQ3C2
       DSNAQ3C3
       DSNAQ3C4
       DSNAQ3C5
       DSNAQ3C6
       DSNAQ3C7
       DSNAQ3C8
       DSNAQ3C9
       DSNAQ6CC
       DSNAQ6CE
       DSNAQ6CF
       DSNAQ6CM
       DSNAQ6C0
       DSNAQ6C1
       DSNAQ6C2
       DSNAQ6C3
       DSNAQ6C4
       DSNAQ6C5
       DSNAQ6C6
       DSNAQ6C7
       DSNAQ6C9

      MACROS
       DSNAQJBA
       DSNAQJBB
       DSNAQJB1
       DSNAQJB2
       DSNAQJB3
       DSNAQJB4
       DSNAQJB5
       DSNAQJB6
       DSNAQJB7
       DSNAQJB8
       DSNAQJC1
1      DSNAQJC2
       DSNAQJC3
       DSNAQJC4
       DSNAQJRM
       DSNAQJS1
       DSNAQJS2
       DSNAQ3E1

      LISTEND
 UK96839 COVER LETTER END


 UK96845 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89693 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 and DB2 9 users of workfiles or   *
        *                 created global temporary tables (CGTT)       *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C4 DSNIWKFD+0FC6 during abort     *
        *                      path of workfile or CGTT application    *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        A workfile or CGTT application entered abort (e.g. due to cancel
        or any other reason) while DB2 was in the middle of deleting a
        workfile, at a point after the internal OBDREC structure had
        already been freed but before a pointer to it was reset.

        Once in abort path, as a result of the still non-zero pointer,
        DB2 attempted to free the OBDREC structure for a second time.
        Code has been changed to properly manage the pointer to the
        internal OBDREC structure during workfile delete path.

        Additional keywords: SQLCGTT OFFSET0FC6
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89693
    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  PM89693

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89693   DSNIWKFD

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIWKFD

      LISTEND
 UK96845 COVER LETTER END


1UK96847 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89898 -
        ****************************************************************
        * USERS AFFECTED: All Users of the IBM Data                    *
        *                 Server Driver for JDBC and SQLJ              *
        *                                                              *
        ****************************************************************
        * PROBLEM DESCRIPTION: IBM Data Sever Driver for JDBC and      *
        *                      SQLJ version 4.15.99 is provided by     *
        *                      this APAR ( JCCV41599 )                 *
        *                                                              *
        *                      This APAR is applicable to IBM Data     *
        *                      Sever Driver for JDBC and SQLJ          *
        *                      for DB2 z/OS V11, DB2 z/OS V10 and      *
        *                      DB2 z/OS V9( JCCZOSDB2V11,              *
        *                      JCCZOSDB2V10, JCCZOSDB2V9 )             *
        *                                                              *
        *                      This APAR delivers a new release (4.15) *
        *                      of the IBM Data Server Driver for JDBC  *
        *                      and SQLJ providing an accumulation of   *
        *                      defect fixes and enhancements.          *
        *                                                              *
        *                      Individual items are documented in the  *
        *                      APAR summary section that follows.      *
        *                                                              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        JCC sub-category keywords:
            JCCCOMMON, JCCT2ZOS, JCCT4, JCCT4XA, JCCSQLJ

        The following changes are delivered in this APAR:
        _______________________________________________________________
        Type-2 z/OS connectivity: Various minor improvements to
        make loading the driver and connection establishment less
        expensive in terms of CPU and memory.(RTC 30648)
        _______________________________________________________________
        Type-2 z/OS connectivity: SQLJ application encounters data
        corruption in a multithreaded environment. This happens when
        callableStatement is executed under WAS with statement
        caching enabled. This issue is fixed.(RTC 30234 )
        _______________________________________________________________
        Type-4 connectivity: When using client affinities with an
        affinityFailbackInterval value the driver does not fail back
        to the primary server, even though the server may have
        become available. This issue is fixed.(RTC 32630)
        _______________________________________________________________
        Type-4 XA Connectivity: Driver does not close 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. (RTC 28121)
        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
1   APARS FIXED: PM89898
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR02 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        ***Action for PM58952

        ____________________________________________________________
        This PTF contains a fix for a defect in the SQLJ translator.
        Incorrect code was generated for an SQL SELECT INTO statement
        using a common table expression specified with the "WITH"
        keyword. To make this fix effective for any impacted SQLJ
        program, after applying the APAR, you must re-translate the
        SQLJ program, then you must run the SQLJ Binder (db2sqljbind)
        again on the affected profiles and rebind the profiles.

        See PM58952 APAR/PTF text in the PTF cover letter for
        further information about this problem. Reference entry
        with (wsdbu01043533) identifier.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNAJJC1  PM89898
       DSNAJJC2  PM89898
       DSNAJ3CC  PM89898
       DSNAJ3CE  PM89898
       DSNAJ3CF  PM89898
       DSNAJ3CM  PM89898
       DSNAJ3C0  PM89898
       DSNAJ3C1  PM89898
       DSNAJ3C2  PM89898
       DSNAJ3C3  PM89898
       DSNAJ3C4  PM89898
       DSNAJ3C5  PM89898
       DSNAJ3C6  PM89898
       DSNAJ3C7  PM89898
       DSNAJ3C9  PM89898
       DSNAJ6CC  PM89898
       DSNAJ6CE  PM89898
       DSNAJ6CF  PM89898
       DSNAJ6CM  PM89898
       DSNAJ6C0  PM89898
       DSNAJ6C1  PM89898
       DSNAJ6C2  PM89898
       DSNAJ6C3  PM89898
       DSNAJ6C4  PM89898
       DSNAJ6C5  PM89898
       DSNAJ6C6  PM89898
       DSNAJ6C7  PM89898
       DSNAJ6C9  PM89898

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89898   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
1
      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNAJ3CC
       DSNAJ3CE
       DSNAJ3CF
       DSNAJ3CM
       DSNAJ3C0
       DSNAJ3C1
       DSNAJ3C2
       DSNAJ3C3
       DSNAJ3C4
       DSNAJ3C5
       DSNAJ3C6
       DSNAJ3C7
       DSNAJ3C9
       DSNAJ6CC
       DSNAJ6CE
       DSNAJ6CF
       DSNAJ6CM
       DSNAJ6C0
       DSNAJ6C1
       DSNAJ6C2
       DSNAJ6C3
       DSNAJ6C4
       DSNAJ6C5
       DSNAJ6C6
       DSNAJ6C7
       DSNAJ6C9

      MACROS
       DSNAJJC1
       DSNAJJC2

      LISTEND
 UK96847 COVER LETTER END


 UK96850 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM94435 -
        ****************************************************************
        * USERS AFFECTED: DB2 users using more than 25 buffer pools    *
        *                 and IFCID 2 overflow trace records with      *
        *                 UK94096 or UK95295 applied.                  *
        ****************************************************************
        * PROBLEM DESCRIPTION: An IFCID 2 overflow trace record        *
        *                      contains an incorrect record length     *
        *                      due to a missing recompile of a module  *
        *                      that sets the record length.            *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When more than 25 buffer pools are allocated, an IFCID 2
        overflow trace record contains an incorrect record length.
1       The incorrect length impacts the buffer pool statistic mapping
        starting from the 26th buffer pool and beyond and causes an
        incorrect count to appear in the Statistics report.
        DB2 has been fixed to recompile a module that stores the
        length of an IFCID 2 overflow trace record.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM94435
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNB1TSD  PM94435
       DSNWVZD1  PM94435

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM94435   DSNB1TSD DSNWVZD1

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNB1TSD
       DSNWVZD1

      LISTEND
 UK96850 COVER LETTER END


 UK96852 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90717 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 or DB2 10 for z/OS users           *
        ****************************************************************
        * PROBLEM DESCRIPTION: False Page regression detected          *
        *                      by DSN1LOGP with the CHECK(DATA)        *
        *                      option due to page LRSN value not       *
        *                      updated properly.                       *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Log apply redo process did not update the space map page's
        PGLOGRBA, this made DSN1LOGP process think the page was
        not serialized due to page's LRSN/RBA out of sequence. This
        issue does not cause any actual data page or smap page
        regression, but it needs to be fixed for avoiding false alarm.
        DB2 module DSNIUSME is modified to always update PGLOGRBA
        value of the space map page after the redo log is applied.
        This serves as a serviceability code for diagnosis.

        ------------------ serviceability apar ------------------

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM90717
    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
       DSNIUSME  PM90717

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90717   DSNIUSME

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIUSME

      LISTEND
 UK96852 COVER LETTER END


 UK96857 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89670 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS , DB2 10 for z/OS and DB2 *
        *                 11 for z/OS users of CHECK INDEX             *
        ****************************************************************
        * PROBLEM DESCRIPTION: CHECK INDEX on partitioned index may    *
        *                      issue MSGDSNU719I with incorrect count  *
        *                      of checked entries                      *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available.         *
        ****************************************************************
        User ran a CHECK INDEX utility on a partitioned index with
        272192175 entries.  The index was checked in parallel and the
        job finished with RC0.  But in the job output, there was:

        DSNU719I DSNUKPIK - 270824328 ENTRIES CHECKED FOR INDEX 'TD.IX1'

        The count of entries checked reported in the DSNU719I was not
        equal to the actual number of entries in the index. The problem
        happened because the number reported in DSNU719I was not counted
        correctly.

        The problem can happen intermittently and it is only the count
        in message DSNU719I that is incorrect, the result of CHECK INDEX
        is still correct.
        CHECK INDEX utility has been modified to report the correct
        count of entries checked in MSGDSNU719I.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89670
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUKIKI  PM89670

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1      PM89670   DSNUKIKI

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUKIKI

      LISTEND
 UK96857 COVER LETTER END


 UK96871 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM87844 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS      *
        *                 users of LOAD and REORG TABLESPACE utility   *
        *                 with the PREFORMAT keyword                   *
        ****************************************************************
        * PROBLEM DESCRIPTION: Enable PREFORMAT on LOB table space and *
        *                      auxiliary index during LOAD and REORG   *
        *                      AUX YES execution.                      *
        ****************************************************************
        * RECOMMENDATION: Apply PTF when available.                    *
        ****************************************************************
        Prior to this APAR, LOAD SHRLEVEL NONE and REORG AUX YES do not
        preformat the affected LOB table spaces and auxiliary indexes
        when PREFORMAT is specified.  The objective of this APAR is to
        extend the PREFORMAT option to LOB table spaces and auxiliary
        indexes serialized by these utilities.  This is done to minimize
        the performance penalty caused by formatting of LOB data pages
        during subsequent SQL operations.

        This APAR introduces the following changes to externals:

        The Utility Guide and Reference has been updated as follows:

        Under the REORG TABLESPACE keyword section:

          PREFORMAT

          Specifies that the remaining pages are to be preformatted up
        | to the high allocated RBA in the table space and index spaces
        | that are associated with the table space or partitions that
        | are being reorganized.  The preformatting occurs after the
          data is loaded and the indexes are built.

          PREFORMAT can operate on an entire table space and its index
          spaces, or on a partition of a partitioned table space and
        | its corresponding partitioning index space.  When AUX YES
        | is specified or accepted as the default, the LOB table spaces
        | and auxiliary indexes that are associated with the base
        | partitions that are being reorganized are also preformatted at
        | the end of RELOAD phase.

          ...
1
        Under the LOAD keyword section:

          PREFORMAT

          Specifies that the remaining pages are preformatted up to the
          high-allocated RBA in the table space and index space that
          are associated with the table that is specified in table.name.
          The preformatting occurs after the data has been loaded and
          the indexes are built.

          PREFORMAT can operate on an entire table space and its index
          spaces, or on a partition of a partitioned table space and on
          the corresponding partitions of partitioned indexes, if any
          exist.  Specifying LOAD PREFORMAT (rather than PART integer
          PREFORMAT) tells LOAD to serialize at the table space level,
          which can inhibit concurrent processing of separate
          partitions.  If you want to serialize at the partition level,
          specify PART integer PREFORMAT.  See "Option descriptions for
          INTO TABLE" for information about specifying PREFORMAT at the
          partition level.

        | The PREFORMAT keyword also applies to LOB table spaces and
        | auxiliary indexes that are associated with the base table or
        | partitions that LOAD serialized.  XML objects are not
        | preformatted.

        Code has been modified to extend the data set preformats to
        LOB table spaces and auxiliary indexes in LOAD SHRLEVEL NONE
        and REORG AUX YES execution with PREFORMAT.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM87844
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        The PTF of APAR PM87844 has extended the PREFORMAT function
        of the LOAD SHRLEVEL NONE and REORG AUX YES utility to support
        preformatting of LOB table spaces and auxiliary index being
        processed.  The auxiliary pagesets would be preformatted up to
        its HARP value automatically when PREFORMAT is specified, and
        no other user action is required.

        APAR PM87844 introduces the following changes to externals:

        Utility Guide and Reference is updated as follows:

        Under the REORG TABLESPACE keyword section:

          PREFORMAT

          Specifies that the remaining pages are to be preformatted up
        | to the high-allocated RBA in the table space and index spaces
        | that are associated with the table space or partitions that
          are being reorganized.  The preformatting occurs after the
          data is loaded and the indexes are built.
1
          PREFORMAT can operate on an entire table space and its index
          spaces, or on a partition of a partitioned table space and
        | its corresponding partitioning index space.  When AUX YES
        | is specified or accepted as the default, the LOB table spaces
        | and auxiliary indexes that are associated with the base
        | partitions that are being reorganized are also preformatted at
        | the end of RELOAD phase.

          ...

        Under the LOAD keyword section:

          PREFORMAT

          Specifies that the remaining pages are preformatted up to the
          high-allocated RBA in the table space and index space that
          are associated with the table that is specified in table.name.
          The preformatting occurs after the data has been loaded and
          the indexes are built.

          PREFORMAT can operate on an entire table space and its index
          spaces, or on a partition of a partitioned table space and on
          the corresponding partitions of partitioned indexes, if any
          exist.  Specifying LOAD PREFORMAT (rather than PART integer
          PREFORMAT) tells LOAD to serialize at the table space level,
          which can inhibit concurrent processing of separate
          partitions.  If you want to serialize at the partition level,
          specify PART integer PREFORMAT.  See "Option descriptions for
          INTO TABLE" for information about specifying PREFORMAT at the
          partition level.

        | The PREFORMAT keyword also applies to LOB table spaces and
        | auxiliary indexes that are associated with the base table or
        | partitions that LOAD serialized.  XML objects are not
        | preformatted.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNURWI   PM87844
       DSNURWT   PM87844

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM87844   DSNURWI  DSNURWT

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNURWI
       DSNURWT

      LISTEND
 UK96871 COVER LETTER END


 UK96875 COVER LETTER START
    PROBLEM DESCRIPTION(S):
1     PM87504 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS, DB2 10 for z/OS and DB2  *
        *                 11 for z/OS utility users of LOAD            *
        ****************************************************************
        * PROBLEM DESCRIPTION: RESTART PHASE of a LOAD utility that    *
        *                      had abended in the SORTBLD phase,       *
        *                      abends with ABENDS0C4 at DSNURILD       *
        *                      +x'627E'                                *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        A LOAD utility executing with parallel index build abended in
        the SORTBLD phase and was restarted.  However, instead of
        specifying the same data set for the SYSREC, NULLFILE was
        specified.  Because this was a restart, certain parallel index
        build control block settings remained, but because of the
        NULLFILE, it was not invoked which, in turn, did not allocate
        other control blocks.  When an attempt was made to access one of
        these missing control blocks the ABENDS0C4 at DSNURILD
        OFFSET627E occurred.
        LOAD restart processing code has been modified to reinitialize
        the parallel index build flag during initialization processing.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM87504
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNURWI   PM87504

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM87504   DSNURWI

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNURWI

      LISTEND
 UK96875 COVER LETTER END


 UK96879 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90984 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS, DB2 10 for z/OS, and     *
        *                 DB2 11 for z/OS users of the                 *
        *                 REORG TABLESPACE and RECOVER utilities.      *
        ****************************************************************
        * PROBLEM DESCRIPTION: This APAR is fixing three distinct      *
        *                      problems: two with the REORG utility    *
        *                      and one with the RECOVER utility.       *
        *                                                              *
1       *                      1. After an AUX YES REORG of the DBD01  *
        *                         directory table space with inline    *
        *                         image copies being taken, a REORG    *
        *                         of the DSNDB01.SYSDBDXA LOB table    *
        *                         space failed RC=8 with message       *
        *                         DSNU341I being displayed. This is    *
        *                         a problem in DB2 10 for z/OS NFM     *
        *                         and all modes in DB2 11 for z/OS.    *
        *                                                              *
        *                      2. After a LOG NO REORG of directory    *
        *                         table space DSNDB01.DBD01 and        *
        *                         catalog table space DSNDB06.SYSCOPY, *
        *                         the DSNAME field of the REPORT       *
        *                         RECOVERY DSNU582I message is blank.  *
        *                                                              *
        *                      3. ABEND04E RC00C90101 DSNIZLDR: 5002   *
        *                         may occur during RESTART of the      *
        *                         RECOVER utility in the RESTORE       *
        *                         phase.                               *
        *                                                              *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        Three problems are corrected in this APAR: two in the REORG
        utility and one in the RECOVER utility.

        1. A REORG of DSNDB01.DBD01 was done with AUX YES specified so
           that it's LOB table space would also be processed. Inline
           image copies were taken of both the DBD01 and SYSDBDXA table
           spaces during REORG processing.

           A subsequent REORG of the SYSDBDXA LOB table space failed
           RC=8 with message MSGDSNU341I being displayed:


           DSNU341I  -DB2A 163 16:05:37.48 DSNURFIT - IMAGE COPY MUST
                      BE TAKEN BEFORE REORG CAN BE RUN ON A DB2 CATALOG
                      OR DIRECTORY TABLESPACE: DSNDB01.SYSDBDXA

           This problem happens in DB2 10 NFM and all modes in V11.


        2. LOG NO REORGs of catalog and directory table spaces whose
           SYSCOPY log records are written to the DB2 logs will have a
           blank DSNAME field in REPORT RECOVERY's MSGDSNU582I message.

           This happens in V9 through V11 for the following table
           spaces:

               DSNDB01.DBD01

           This also happens in V10 ENFM through V11 for the following
           new directory LOB table space:

               DSNDB01.SYSDBDXA

1          The new LOB table space above is created as the V10 ENFM
           process progresses.


           This also happens for DSNDB06.SYSCOPY in V9 through V11
           ENFM during which it's replaced by the DSNDB06.SYSTSCPY
           catalog table space. Once DSNDB06.SYSTSCPY is created, it
           too would have the reported problem.


        3. ABEND04E RC00C90101 in DSNIZLDR ERQUAL5002 may occur during
           RESTART of the RECOVER utility in the RESTORE phase when one
           of the objects being recovered is a compressed table space.
           The customer's test scenario was:

             a. RECOVER TABLESPACE ...  TOCOPY (data-set-name)
             b. Purposely crash DB2 while RECOVER is in the RESTORE
                phase
             c. Resubmit the RECOVER job so that it restarts from the
                last commit taken in the RESTORE phase results in an
                ABEND04E RC00C90101

           The abend occurred during RESTART of the RECOVER during the
           open of the table space because the dictionary pages were
           missing. The dictionary pages were missing because the first
           invocation of the RECOVER utility did not correctly force
           the pages restored to the table space from the image copy
           from the buffer pool to disk at commit intervals during the
           RESTORE phase. This problem could occur for any type of
           RECOVER with a RESTORE phase, not just when the TOCOPY
           option has been specified.

        DB2 code has been updated as follows for each of the three fixes
        noted for this APAR:

        1. Inline image copies taken during REORG processing for the
           DSNDB01.SYSDBDXA table space will be properly recorded. This
           will allow subsequent REORGs of the DSNDB01.SYSDBDXA table
           space to work without having to first take another image
           copy.

        2. LOG NO REORGs will now properly fill in SYSCOPY.DSNAME for
           the following directory and catalog objects:

             DSNDB01.DBD01
             DSNDB01.SYSDBDXA
             DSNDB06.SYSCOPY
             DSNDB06.SYSTSCPY

        3. The RECOVER utility now correctly forces pages restored to
           the table space from the buffer pool to disk at commit
           intervals during the RESTORE phase.

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM90984
    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
       DSNUCAWR  PM90984
       DSNUCAWT  PM90984
       DSNULOG1  PM90984
       DSNURWT   PM90984

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90984   DSNUCAWR DSNUCAWT DSNULOG1 DSNURWT

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUCAWR
       DSNUCAWT
       DSNULOG1
       DSNURWT

      LISTEND
 UK96879 COVER LETTER END


 UK96886 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM87248 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS with PM70915 (UK83425)    *
        *                 applied, DB2 10 for z/OS with PM70915        *
        *                 (UK83424) applied and DB2 11 for z/OS        *
        *                 utility users                                *
        ****************************************************************
        * PROBLEM DESCRIPTION: REORG TABLESPACE COPYDDN with the       *
        *                      inline copy going to tape fails with    *
        *                      ABEND04E RC00E40311 at DSNUGCMA         *
        *                      +x'05B6' after an ABEND0C4 at IGX00032  *
        *                      OFFSET01C0                              *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        For DB2 10 for z/OS having PM70915 (UK83424) applied and running
        on z/OS level 1.12, REORG TABLESPACE COPYDDN with the inline
        copy going to tape abends with ABEND04E RC00E40311.  This abend
        was the normal REORG response to DFSMS incurring an ABEND0C4 at
        IGX00032 +x'01C0'.

        The ABENDS0C4 occurred when DFSMS attempted to access a 31-bit
        UCB address using a 24-bit pointer.  DB2 APAR PM52891 allowed
        DB2 to access some of these DFSMS control blocks and PM70915
        fixed a problem accessing a 31-bit UCB.

        DB2 has no code error in this case; the problem is in DFSMS code
        and fixed by APAR OA41617 which must be applied.

        This error can also occur on DB2 9 for z/OS with PM70915
1       (UK83425) applied at z/OS 1.12 or higher or DB2 11 at z/OS 1.13
        or higher.  In all cases, NON_VSAM_XTIOT must be set to YES in
        DEVSUPxx in order for the possibility for the DFSMS abend to
        occur.
        DFSMS APAR OA41617 must be applied to fix the reported problem.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM87248
    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  PM87248

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM87248   DSNUGDYN

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUGDYN

      LISTEND
 UK96886 COVER LETTER END


 UK96896 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM94538 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 10 for z/OS ODBC/CLI        *
        *                 running with MULTICONTEXT=2.                 *
        ****************************************************************
        * PROBLEM DESCRIPTION: An SQL call on an ODBC connection using *
        *                      MULTICONTEXT=2 may get an ABEND0C4 if   *
        *                      DSNARRS has been released via an MVS    *
        *                      DELETE, due to incorrect connection     *
        *                      processing.                             *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When running with MULTICONTEXT=2, a connection handle may be
        switched away from the task that created it.  If the task
        proceeds to terminate leaving the connection handle allocated,
        the DSNARRS load count may be decremented resulting in DSNARRS
        being removed from virtual storage.  If another task uses the
        connection handle when DSNARRS has been deleted, an ABEND0C4
        may occur on the call to DSNARRS.

        Specification of MULTICONTEXT=2 enables a multithreaded ODBC
        application to always maintain an active environment handle
        under a designated LE thread in a multiple-context environment.
        MULTICONTEXT=2 is to be used only under the direction of
1       IBM Software Support.
        This APAR will require DB2 APAR PM94536 where a mechanism will
        be provided to allow ODBC to signal DB2 when MULTICONTEXT=2
        is specified in the intialization file.  Upon receiving the
        signal, DSNRLI will avoid doing an MVS DELETE of DSNARRS.

        To fully implement this APAR fix, it must be installed together
        with PM94536.  If PM94536 is not installed, then the fix
        delivered by this APAR will not be enabled.
    COMPONENT:  5740-XYR02-JDBAA17
    APARS FIXED: PM94538
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR02 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        *** Action for PM94538 (Version 10)

        This APAR PM94538, together with DB2 APAR PM94536, provides
        a mechanism to prevent load module DSNARRS from being
        prematurely deleted when MULTICONTEXT=2.  To fully implement
        this APAR fix, it must be installed together with PM94536.
        If PM94536 is not installed, then the fix delivered by this
        APAR will not be enabled.

        Specification of MULTICONTEXT=2 enables a multithreaded ODBC
        application to always maintain an active environment handle
        under a designated LE thread in a multiple-context environment.
        MULTICONTEXT=2 is to be used only under the direction of
        IBM Software Support.

        Complete documentation for MULTICONTEXT=2 will be provided
        in the DB2 10 for z/OS ODBC Guide and Reference and in the
        Information Management Software for z/OS Solutions Information
        Center at a later date.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       CLIMVSF6  PM94538
       DSNAOG0J  PM94538
       DSNAOCLI  PM94538
       DSNAOSDK  PM94538

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM94538   CLIMVSF6 DSNAOG0J DSNAOCLI DSNAOSDK

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       CLIMVSF6
       DSNAOG0J
       DSNAOCLI

      MACROS
       DSNAOSDK

      LISTEND
 UK96896 COVER LETTER END
1

 UK96919 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM91839 -
        ****************************************************************
        * USERS AFFECTED: DB2 10 for z/OS and DB2 11 for z/OS          *
        *                 customers with queries eligible for          *
        *                 range list access.                           *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C4 in DSNXOCCX may occur during   *
        *                      query optimization for queries eligible *
        *                      for range list access.                  *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        ABEND0C4 in DSNXOCCX may occur during query optimization for
        queries eligible for range list access (ACCESSTYPE='NR' in the
        PLAN_TABLE).

        This abend occurs because DB2 incorrectly references undefined
        storage.  As such, the abend may be intermittent.

        Depending on the maintenance level of DSNXOCCX, the abend
        could occur at one of the following locations:
          DSNXOCCX +2384
          DSNXOCCX +237E
          DSNXOCCX +2086

        Additional keywords:
        SQLRANGELIST RANGELIST SQLOR OFFSET2384 OFFSET237E OFFSET2086
        DB2 code has been fixed to avoid referencing undefined storage.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM91839
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOCCX  PM91839
       DSNXOGOR  PM91839

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM91839   DSNXOCCX DSNXOGOR

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOCCX
       DSNXOGOR

      LISTEND
 UK96919 COVER LETTER END


 UK96925 COVER LETTER START
1   PROBLEM DESCRIPTION(S):
      PM94156 -
        ****************************************************************
        * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
        *                 Specifically where DB2 is configured to      *
        *                 establish a trusted connection to a remote   *
        *                 DB2/LUW server where the actual trusted      *
        *                 context is not defined for this connection.  *
        ****************************************************************
        * PROBLEM DESCRIPTION: Message DSNL031I (with DSNLZDJN REASON  *
        *                      00D351FF and ERROR ID DSNLZRPA0001)     *
        *                      and SQLCODE -30020 (with 1245 0210      *
        *                      DSNLZRSQ), instead of SQLCODE +20360,   *
        *                      when accessing a remote DB2/LUW server  *
        *                      where the associated trusted context    *
        *                      is not defined.                         *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The user populates the DB2 for z/OS Communications Data Base
        tables to access a remote DB2/LUW server via a trusted
        connection.  The actual trusted context is not defined at the
        remote DB2/LUW server to allow this trusted connection.  In
        this situation, an SQLCODE +20360 should be returned to the
        application.  However a DB2/LUW server associates the condition
        with a DRDA SVRCOD value that the DB2 for z/OS requester does
        not expect.
        As a result, the DB2 for z/OS requester incorrectly believes
        that the trusted connection was actually accepted and therefore
        initiates a DRDA "switch user" sequence.  The server rejects
        the switch user sequence (with a DRDA PRCCNVRM) since the
        connection is not actually trusted.  As a result, the DB2 z/OS
        requester issues message DSNL031I and returns a -30020 to the
        application.

        DB2 for z/OS requester processing has been changed to
        anticipate a DRDA SVRCOD=0 value from a DB2/LUW server when the
        trusted connection request fails.  This allows SQLCODE +20360
        to be returned to the application as an indication that the
        connection to the DB2/LUW server can still be utilized, but as
        non trusted.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM94156
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNLTAC1  PM94156

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM94156   DSNLTAC1

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
1      DSNLTAC1

      LISTEND
 UK96925 COVER LETTER END


 UK96933 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88830 -
        ****************************************************************
        * USERS AFFECTED: ALL DB2 9 and DB2 10 for z/OS users.         *
        ****************************************************************
        * PROBLEM DESCRIPTION: Several problems are addressed here.    *
        *                                                              *
        *                      1.  On DB2 9 and DB2 10 for z/OS,       *
        *                        ABEND04E 00C90101 in DSNIIMSI 5010    *
        *                        for a SELECT statement                *
        *                      2.  On DB2 9 and DB2 10 for z/OS,       *
        *                        ABEND04E 0070005 in DSNXEFDA M500     *
        *                        for a SELECT statement.               *
        *                      3.  On DB2 10 for z/OS,                 *
        *                        ABEND04E 0070005 in DSNXOOP M600      *
        *                        for a SELECT statement with           *
        *                        CONCENTRATE STATEMENT WITH LITERALS   *
        *                        set.                                  *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Several problems are addressed here.

        1.  On DB2 9 and DB2 10 for z/OS,
          ABEND04E 00C90101 in DSNIIMSI 5010
          for a SELECT statement
        2.  On DB2 9 and DB2 10 for z/OS,
          ABEND04E 0070005 in DSNXEFDA M500
          for a SELECT statement.
        3.  On DB2 10 for z/OS,
          ABEND04E 0070005 in DSNXOOP M600
          for a SELECT statement with
          CONCENTRATE STATEMENT WITH LITERALS
          set.

        Problems 1 and 2 are rare conditions that
        occur when there is a system error on an
        optional process during bind/prepare.
        Problem 3 occurs when multiple encoding
        schemes are used within a statement.
        DB2 has been fixed to handle the problems described.

        Additional Keywords:  SQLSELECT SQLDYNSTMTCACHE
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88830
    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
       DSNXODTR  PM88830
       DSNXOPML  PM88830
       DSNXORHV  PM88830
       DSNXOTPL  PM88830

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88830   DSNXODTR DSNXOPML DSNXORHV DSNXOTPL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXODTR
       DSNXOPML
       DSNXORHV
       DSNXOTPL

      LISTEND
 UK96933 COVER LETTER END


 UK96935 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM92293 -
        ****************************************************************
        * USERS AFFECTED: All DB2 users of the IBM Data Analytics      *
        *                 Accelerator (IDAA).                          *
        ****************************************************************
        * PROBLEM DESCRIPTION: The following symptoms may appear       *
        *                      during a query offload to IDAA:         *
        *                      . Abend 04E-00D35011                    *
        *                        LOC=DSNLZGLM.DSNLZRTM:0878            *
        *                        followed by                           *
        *                      . Abend 04F-00E50702 and abnormal       *
        *                        termination of the DB2 subsystem.     *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        A remote client application connects to a DB2 for z/OS server
        and executes a query which is offloaded to IDAA.  Before the
        query could complete execution on IDAA, the client application
        terminated its connection to DB2.  During abort processing, DB2
        references an internal control block which had already been
        freed, leading to the 04E-00D35011 abend.  If the 04E-00D35011
        abend occurs during must complete processing, it will result in
        the termination of the DB2 subsystem with abend 04F-00E50702 and
        message DSNV086E DB2 ABNORMAL TERMINATION REASON=00E50702.

        DB2 query offload and abort processing is corrected to not
        reference freed internal control blocks.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM92293
    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
       DSNLXCMT  PM92293
       DSNLXRBF  PM92293
       DSNLXRCL  PM92293
       DSNLXREL  PM92293
       DSNLXRFT  PM92293
       DSNLXROP  PM92293
       DSNLXRSQ  PM92293
       DSNLXRUW  PM92293
       DSNLXSRX  PM92293

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM92293   DSNLXCMT DSNLXRBF DSNLXRCL DSNLXREL DSNLXRFT DSNLXROP
                 DSNLXRSQ DSNLXRUW DSNLXSRX

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNLXCMT
       DSNLXRBF
       DSNLXRCL
       DSNLXREL
       DSNLXRFT
       DSNLXROP
       DSNLXRSQ
       DSNLXRUW
       DSNLXSRX

      LISTEND
 UK96935 COVER LETTER END


 UK96950 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM92532 -
        ****************************************************************
        * USERS AFFECTED: DB2 10 for z/OS users who received one       *
        *                 or more rows from the ++HOLD query of        *
        *                 PM78210 / UK90728                            *
        ****************************************************************
        * PROBLEM DESCRIPTION: The query provided in the ++HOLD        *
        *                      of PM78210/UK90728 may incorrectly      *
        *                      return table spaces which are Basic     *
        *                      Row Format (BRF) that do not            *
        *                      contain tables with inline LOBs.        *
        *                                                              *
        *                      PM78210/UK90728 does not need to        *
        *                      be removed, only the ++HOLD query       *
        *                      needs to be updated.                    *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The query provided in the ++HOLD of PM78210/UK90728 may
        incorrectly return BRF table spaces that do not contain
        tables with inline LOB columns. This may occur when a view
        is defined on multiple tables, with one table residing in
1       a BRF table space that contains no inline LOB columns and
        another table residing in a Reordered Row Format (RRF)
        table space which contains an inline LOB column.
        The query provided in the ++HOLD of PM78210/UK90728 has
        been updated to exclude views.

        PM78210 fixes CREATE TABLE to define implicit table spaces
        as 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' );

        ADDITIONAL KEYWORDS:
        RC00C90101
        ABNDID5005
        DB2LOB
        SQLLOB
        INCORROUT
        SQLINCORR
        SQLINCORROUT

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM92532
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
1     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
        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,
1              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 = ' ' );
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXICTB  PM92532

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM92532   DSNXICTB

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXICTB

      LISTEND
 UK96950 COVER LETTER END


 UK96951 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM92807 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 9, 10 and 11 for z/OS       *
        *                 who are also using IBM DB2 Analytics         *
        *                 Accelerator                                  *
        ****************************************************************
        * PROBLEM DESCRIPTION: SQLCODE -901 is incorrectly issued      *
        *                      when a float literal is used and        *
        *                      DSNHDECP.DECIMAL=COMMA                  *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        SQLCODE -901 is incorrectly issued when a float literal is used
        and DSNHDECP.DECIMAL=COMMA
        Code is fixed to offload the query.

        Additional Search Keywords:
        IDAAV3R1/K IDAAV2R1/K SQLCODE901
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM92807
    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
       DSNXONZC  PM92807

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM92807   DSNXONZC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXONZC

      LISTEND
 UK96951 COVER LETTER END


 UK96954 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90713 -
        ****************************************************************
        * USERS AFFECTED: All IRLM220 (HIR2220) and IRLM230 (HIR2230)  *
        *                 users who have applied UK91219/UK91220.      *
        ****************************************************************
        * PROBLEM DESCRIPTION: MSGDXR175E may appear on console for    *
        *                      ECSA storage shortage, which may be     *
        *                      followed by IRA100E for SQA shortage.   *
        *                      IRLM 2.3 may ABEND0C1 in dxrrl400.      *
        ****************************************************************
        * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
        ****************************************************************
        IRLM 2.2 PTF UK91219 for PM71945 did not compile the right
        csect so it did not include the code change for PM71945.
        IRLM 2.3 fix in PTF UK91220 may cause an ABEND0C1 in IRLM
        storage manager module DXRRL400 when FREEMAIN is called
        to release the storage and the base register may be re-used
        causing a wild branch.
        This APAR corrects the fix for PM71945. On a GETMAIN request, if
        MVS returns a common storage below the line (CSA) to IRLM, IRLM
        will FREEMAIN that storage and will set an out-of-storage return
        code. IRLM will also set the base registers correctly after the
        FREEMAIN call to avoid a wild branch from DXRRL400 which could
        lead to ABEND0C1 and IRLM termination.
    COMPONENT:  5695-16401-HIR2230
    APARS FIXED: PM90713
    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  PM90713

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90713   DXRRL400

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

1     MODULES
       DXRRL400

      LISTEND
 UK96954 COVER LETTER END


 UK96958 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM80883 -
        ****************************************************************
        * USERS AFFECTED: All HIR2220 (IRLM220) and HIR2230 (IRLM230)  *
        *                 users in DATASHARING SYSPLEXDS.              *
        ****************************************************************
        * PROBLEM DESCRIPTION: An attempt to get an element from the   *
        *                      NSP pool for a NOTIFY request resulted  *
        *                      in an S0C4 abend in DXRRL400.           *
        ****************************************************************
        * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
        ****************************************************************
        A previously freed element from the NSP pool had garbage in its
        high-half address.  This invalid address caused the S0C4 abend
        when this element was assigned.

        GEN:
        KEYWORDS:

        *** END IMS KEYWORDS ***
        Before freeing the element from the NSP pool, the high word of
        its address is cleared to prevent the abendS0C4.

        This APAR also retrofits PM57645 from IRLM230 to IRLM220.
    COMPONENT:  5695-16401-HIR2230
    APARS FIXED: PM80883
    SPECIAL CONDITIONS:
      COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DXRRL110  PM80883

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM80883   DXRRL110

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DXRRL110

      LISTEND
 UK96958 COVER LETTER END


 UK96959 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89139 -
1       ****************************************************************
        * USERS AFFECTED: All HIR2230 (IRLM230) users.                 *
        ****************************************************************
        * PROBLEM DESCRIPTION: IRLM 2.3 enhancements roll-up APAR      *
        ****************************************************************
        * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
        ****************************************************************
        This APAR includes multiple enhancements in IRLM storage
        management, accounting, serviceability and performance.


        1. IRLM 2.3 storage usage monitoring for CSA and IRLM private
           storage is improved for tracking current usage and high water
           marks.  Additional sub-system statistics are provided in a
           STAT requests for:
           - ECSA current & high water mark(HWM)
           - Below the 2G bar PVT current & HWM
           - Above the 2G bar PVT current & HWM
           - PVT threshold above and below the 2G bar
           - Storage sub-pool type statistics (sub-pool name, type info)

           For DB2 V11, DXR100I message is enhanced to show updated
           storage usage and IRLM sub-pool statistics

        2. DXR121I message will also show IRLM private storage used
           below the bar as HI-PVT.  For example:
              DXR121I PR21001 END-OF-TASK CLEANUP SUCCESSFUL - HI-CSA
              HI-ACCT-CSA      0K  -  HI-PVT   5402K

        3. Improvements in IRLM storage management during workload
           spikes to reduce excessive GETMAIN requests and contention
           on CML lock.  IRLM now re-check the free storage chain before
           actually doing the GETMAIN call.  If there is one then IRLM
           will skip the GETMAIN call and it prevents unneccessary pool
           expansion (especially the QEFIX pool) which may causes
           performance problem due to high paging activity in some
           special case.

        4. Reduce DB2 auto-restart failures when an earlier instance of
           IRLM has not completed termination.  IRLM initialization will
           allow for 2 minutes of grace period for an earlier IRLM
           address space to go away, before failing initialization in
           DXRRL010 with ABENDU2019.  DB2 restart will not timeout and
           issue DSNT384I if IRLM can be started within 2 minutes under
           these conditions.

        5. Reduce IRLM SRB CPU time when IRLM is accessing resource hash
           table (RHT) in deadlock setup during deadlock processing in
           every deadlock interval. IRLM will keep waiter information
           for every RHT.  It will scan the entire RHB synonym chain off
           an RHT only when there exists one or more lock waiter on any
           resource on that RHT.  IRLM keeps the waiter information in a
           control block which is always in the top RHB of the same hash
           class. In a workload environment where there are very few
           lock waiters at any time, or most of the lock waiters are
           mostly on few resources only, less CPU time will be spent
1          every deadlock interval, which should give overall
           performance gain.

    COMPONENT:  5695-16401-HIR2230
    APARS FIXED: PM89139
    SPECIAL CONDITIONS:
      COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DXRJCLIN  PM89139
       DXRRL0B0  PM89139
       DXRRL010  PM89139
       DXRRL040  PM89139
       DXRRL090  PM89139
       DXRRL1E0  PM89139
       DXRRL1H9  PM89139
       DXRRL1S0  PM89139
       DXRRL1S1  PM89139
       DXRRL120  PM89139
       DXRRL150  PM89139
       DXRRL160  PM89139
       DXRRL190  PM89139
       DXRRL2B0  PM89139
       DXRRL2R1  PM89139
       DXRRL2R2  PM89139
       DXRRL2R3  PM89139
       DXRRL2R4  PM89139
       DXRRL210  PM89139
       DXRRL211  PM89139
       DXRRL24B  PM89139
       DXRRL24F  PM89139
       DXRRL246  PM89139
       DXRRL247  PM89139
       DXRRL400  PM89139
       DXRRL401  PM89139
       HIR2230J  PM89139

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89139   DXRJCLIN DXRRL0B0 DXRRL010 DXRRL040 DXRRL090 DXRRL1E0
                 DXRRL1H9 DXRRL1S0 DXRRL1S1 DXRRL120 DXRRL150 DXRRL160
                 DXRRL190 DXRRL2B0 DXRRL2R1 DXRRL2R2 DXRRL2R3 DXRRL2R4
                 DXRRL210 DXRRL211 DXRRL24B DXRRL24F DXRRL246 DXRRL247
                 DXRRL400 DXRRL401 HIR2230J

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DXRRL0B0
       DXRRL010
       DXRRL040
       DXRRL090
       DXRRL1E0
       DXRRL1H9
       DXRRL1S0
       DXRRL1S1
1      DXRRL120
       DXRRL150
       DXRRL160
       DXRRL190
       DXRRL2B0
       DXRRL2R1
       DXRRL2R2
       DXRRL2R3
       DXRRL2R4
       DXRRL210
       DXRRL211
       DXRRL24B
       DXRRL24F
       DXRRL246
       DXRRL247
       DXRRL400
       DXRRL401

      MACROS
       DXRJCLIN

      LISTEND
 UK96959 COVER LETTER END


 UK96982 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM95177 -
        ****************************************************************
        * USERS AFFECTED: All data sharing users of DB2 for zOS.       *
        ****************************************************************
        * PROBLEM DESCRIPTION: MSGDSNJ320I issued during DB2 restart   *
        *                      after log truncation and switch.        *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        If a DB2 member of a data sharing group was down during a
        group-wide -ARCHIVE LOG command that resulted in DB2 members
        truncating and switching the active log data sets, the log
        switch will be deferred until the member is restarted.  If
        there are 'destroyed' members in the data sharing group, the
        restarting member will issue MSGDSNJ320I after switching the
        active logs, and the Archive Log Command History record in
        the BSDS will not be updated. DB2 restart will continue.
        DSNJS01A will no longer issue the DSNJ320I error message
        if there is an error accessing a peer member BSDS when
        accumulating Archive Log Command information for the history
        record in the BSDS.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM95177
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNJS01A  PM95177
1
      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM95177   DSNJS01A

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNJS01A

      LISTEND
 UK96982 COVER LETTER END


 UK96987 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM93043 -
        ****************************************************************
        * USERS AFFECTED: DB2 9 for z/OS or DB2 10 for z/OS users with *
        *                 queries specifying either OPTIMIZE FOR 1 ROW *
        *                 or FETCH FIRST 1 ROW ONLY and an ORDER BY    *
        *                 clause                                       *
        ****************************************************************
        * PROBLEM DESCRIPTION: DB2 may select an inefficient access    *
        *                      path for queries with both an ORDER BY  *
        *                      clause and either OPTIMIZE FOR 1 ROW    *
        *                      or FETCH FIRST 1 ROW ONLY.              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        If an index exists with the exact opposite order requested by
        an ORDER BY clause, DB2 can scan the index in reverse to avoid
        a sort for the ORDER BY.

        DB2 may choose an inefficient access path for queries with
        OPTIMIZE FOR 1 ROW or FETCH FIRST 1 ROW when a reverse index
        scan can be used to avoid a sort for an ORDER BY.

        For example,

          SELECT ...
          FROM T1
          WHERE C1 = ?
          ORDER BY C2

        With an index on (C1 ASC, C2 DESC) the index can support the
        ORDER BY, but will require a reverse index scan since the index
        is in order by C2 DESC and the query is requesting order by
        C2 ASC.

        The potential inefficient access path is caused by an
        uninitialized variable.  As such, it is possible that the
        problem is intermittent.

        Additional keywords:
        SQLPERFORMANCE SQLACCESSPATH SQLOFNR SQLFFNR SQLOF1R SQLFF1R
        SQLORDERBY
1       DB2 code has been corrected to properly initialize the
        problem variables.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM93043
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM93043:

        A rebind is necessary for static applications to rebuild
        access paths based on the changes in this APAR.

        PM93043 corrects a problem in which an inefficient access path
        may be selected for a query specifying OPTIMIZE FOR 1 ROW or
        FETCH FIRST 1 ROW and an ORDER BY if an index is available
        to support the ORDER BY in reverse order.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM90987:

        See PM90987 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM90987 corrects a problem of a bad access path for a
        partitioned table when the table is limited to only 1 partition
        for page range access, and there is at least one DPSI on the
        table.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM83144:

        A rebind is necessary for static applications to rebuild
        access paths based on the changes in this APAR.

        PM83144 corrects a problem in which DB2 could incorrectly
        discard an multi-index access path.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM81295:

        See PM81295 APAR/PTF text for additional information about
        why a REBIND is necessary.

1       PM81295 corrects a problem of poor query performance for a
        query containing OR predicates that map to a single index.
        The poor performance can occur when a range-list index access
        plan may not be assigned the lowest cost of any plan it beats.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOCSC  PM93043

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM93043   DSNXOCSC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOCSC

      LISTEND
 UK96987 COVER LETTER END


 UK96992 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88071 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 10 for z/OS who use         *
        *                 IBM DB2 Analytics Accelerator.               *
        ****************************************************************
        * PROBLEM DESCRIPTION: This APAR provides the following new    *
        *                      functions for IBM DB2 Analytics         *
        *                      Accelerator:                            *
        *                                                              *
        *                      (1) Query prioritization support for    *
        *                          remote query offload to an          *
        *                          accelerator.                        *
        *                                                              *
        *                      (2) Enable execution of bit             *
        *                          manipulation functions on an        *
        *                          accelerator.                        *
        *                                                              *
        *                      (3) Enable execution of TIMESTAMPDIFF   *
        *                          on an accelerator.                  *
        *                                                              *
        *                      (4) Enable execution of queries that    *
        *                          involve implicit cast with the      *
        *                          DECFLOAT datatype.                  *
        *                                                              *
        *                      This APAR also fixes the following      *
        *                      problem for IBM DB2 Analytics           *
        *                      Accelerator:                            *
        *                      (5) SQLCODE -901 is incorrectly         *
        *                          issued for a query with the         *
1       *                          TRUNC() scalar function.            *
        *                                                              *
        *                      (6) SQLCODE -904 is incorrectly         *
        *                          issued for a query with             *
        *                          outer joins and table expressions.  *
        *                                                              *
        *                      (7) EXPLAIN may not populate            *
        *                          DSN_QUERYINFO_TABLE with            *
        *                          REASON_CODE = 15 when CURRENT       *
        *                          QUERY ACCELERATION=ENABLE           *
        *                                                              *
        *                      (8) Storage leak occurs for an          *
        *                          INSERT with a common table          *
        *                          expression with row                 *
        *                          permissions.                        *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        This APAR provides the following new functions for IBM DB2
        Analytics Accelerator:

        (1) Query prioritization support for remote query offload to
            an accelerator.

        (2) Enable execution of bit manipulation functions BITAND,
            BITANDNOT, BITOR, BITXOR, and BITNOT on an accelerator.
            The expression, expression1 or expression2 value must be
            SMALLINT, INTEGER, or BIGINT for the function to execute
            on an accelerator.

        (3) Enable execution of TIMESTAMPDIFF
            on an accelerator. The result returned is the accurate
            value that considers leap years and the varying total
            number of days in a month.  This is different than DB2
            behavior, which does not account for leap years and
            calculates that all months have 30 days.

        (4) Enable execution of queries that involve implicit cast with
            the DECFLOAT datatype.  A query will not execute on an
            accelerator if a DECFLOAT column is referenced or if
            a column implicitly cast to DECFLOAT is part of the
            result set.

        This APAR also fixes the following problems for IBM DB2
        Analytics Accelerator:
        (5) SQLCODE -901 is incorrectly issued for a query with the
            TRUNC or TRUNCATE scalar function if numeric-expression-1
            or numeric-expression-2 is not a DECIMAL or FLOAT datatype.
            Code is fixed to offload this query to an accelerator.

        (6) SQLCODE -904 is incorrectly issued for a query that has
            both outer joins and table expressions.  Code is fixed
            to offload this query to an accelerator.

        (7) EXPLAIN may not populate DSN_QUERYINFO_TABLE with
            REASON_CODE = 15 when CURRENT QUERY ACCELERATION=ENABLE.
1           Code is fixed to to populate DSN_QUERYINFO_TABLE correctly.

        (8) Storage leak occurs for an INSERT with a common table
            expression with row permissions.

        Additional Keywords:
        IDAAV3R1/K SQLCODE901 SQLCODE904 SQLTIMESTAMPDIFF SQLBITAND
        SQLOUTERJOIN SQLEXPLAIN SQLCTE SQLINSERT DB2STGLK/K
        SQLACCESSCONTROL SQLTRUNC

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88071
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        **Action for PM83911:

        See PM83911 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM83911 corrects a problem that incorrect output or ABEND04E
        RC00E72018 at the location DSNXGRDS DSNXSBUC OFFSET08EE for V9
        (OFFSET3EA4 for V10) could happen for an SQL statement that
        contains an aggregation function in the ORDER BY clause and the
        aggregation function has an argument referencing a SELECT list
        item that is not a simple column nor a literal constant.

        To make this fix effective for a static application, it must 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
       DSNLXGLM  PM88071
       DSNLXRSQ  PM88071
       DSNXOBFC  PM88071
       DSNXOD5   PM88071
       DSNXOEX1  PM88071
       DSNXONZA  PM88071
       DSNXONZC  PM88071
       DSNXONZO  PM88071
       DSNXONZQ  PM88071
       DSNXONZS  PM88071
       DSNXOOS1  PM88071
       DSNXORFN  PM88071

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88071   DSNLXGLM DSNLXRSQ DSNXOBFC DSNXOD5  DSNXOEX1 DSNXONZA
                 DSNXONZC DSNXONZO DSNXONZQ DSNXONZS DSNXOOS1 DSNXORFN

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNLXGLM
       DSNLXRSQ
1      DSNXOBFC
       DSNXOD5
       DSNXOEX1
       DSNXONZA
       DSNXONZC
       DSNXONZO
       DSNXONZQ
       DSNXONZS
       DSNXOOS1
       DSNXORFN

      LISTEND
 UK96992 COVER LETTER END


 UK97000 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM91561 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users who use *
        *                 the XMLMODIFY function.                      *
        ****************************************************************
        * PROBLEM DESCRIPTION: SQLCODE16002 may be returned when the   *
        *                      XMLMODIFY function is used in the       *
        *                      EBCDIC encoding scheme and the xquery-  *
        *                      update-constant text of the XMLMODIFY   *
        *                      function contains special characters.   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Here is an example to show the failing case.

         =========
          EXAMPLE
         =========

         CREATE TABLE PM91561T (CXML XML) CCSID EBCDIC;

         INSERT INTO PM91561T VALUES('<a>mytest</a>');

         UPDATE PM91561T
         SET CXML = XMLMODIFY('replace value of node /a with '' ''');

        DB2 code has been modified to handle the aforementioned problem
        correctly.

        Additional keywords: SQLCODE16002 SQLENCODING SQLXML
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM91561
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOFN2  PM91561

1     CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM91561   DSNXOFN2

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOFN2

      LISTEND
 UK97000 COVER LETTER END


 UK97002 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM91436 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS  users of DELETE WHERE      *
        *                 CURRENT OF or UPDATE WHERE CURRENT OF        *
        *                 cursors                                      *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C90101 in DSNITDLE with    *
        *                      ERQUAL5005 during DELETE with WHERE     *
        *                      CURRENT OF keyword.                     *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        A pointer to freed storage was used during DELETE WHERE
        CURRENT OF cursor processing which caused DB2 to abend.
        DB2 was modified such that the pointer to the freed
        storage is zeroed out when the storage is freed.

        Additional keywords: SQLDELETE SQLUPDATE
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM91436
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXECL   PM91436
       DSNXECLF  PM91436
       DSNXECLN  PM91436
       DSNXECW   PM91436
       DSNXECWA  PM91436
       DSNXECWU  PM91436

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM91436   DSNXECL  DSNXECLF DSNXECLN DSNXECW  DSNXECWA DSNXECWU

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXECL
       DSNXECLF
       DSNXECLN
       DSNXECW
1      DSNXECWA
       DSNXECWU

      LISTEND
 UK97002 COVER LETTER END


 UK97009 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM92837 -
        ****************************************************************
        * USERS AFFECTED: DB2 9 for z/OS and DB2 10 for z/OS and       *
        *                 DB2 11 for z/OS users of queries containing  *
        *                 join predicates with VARBINARY data type.    *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E at DSNXGRDS.DSNXGINB:M103 may  *
        *                      occur when a query contains join        *
        *                      predicates with VARBINARY data type.    *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        ABEND04E at DSNXGRDS.DSNXGINB:M103 may occur when a query
        contains join predicates with VARBINARY data type.
        The following is an example of a failing query:
        SELECT ....
          FROM T1, T2
         WHERE T1.TIMESTAMPTZ1 = T2.TIMSTAMPTZ1
           AND T1.CHAR10 = T2. VARCHAR6
           AND T1.VARBINARY10 = T2.VARBINARY10
        DB2 is modified to process the VARBINARY join predicate
        correctly.
        Additional keywords: SQLVARBINARY VARBIN
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM92837
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM92837:

        See PM92837 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM92837 corrects a problem of ABEND04E at DSNXGRDS.DSNXGINB:M103
        when a query contains join predicates with 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
       DSNXGINB  PM92837
       DSNXOGA   PM92837

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1      PM92837   DSNXGINB DSNXOGA

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXGINB
       DSNXOGA

      LISTEND
 UK97009 COVER LETTER END


 UK97013 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90568 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS replication product or      *
        *                 IFI 306 users.                               *
        ****************************************************************
        * PROBLEM DESCRIPTION: DB2 for z/OS replication products and   *
        *                      other users of IFI READS of IFCID 306   *
        *                      will receive log records for all tables *
        *                      which are enabled for CAPTURE CHANGES   *
        *                      even in cases where they are interested *
        *                      in only a subset. This results in       *
        *                      unneccesary CPU consumption which could *
        *                      be avoided if there was a way to        *
        *                      qualify which table spaces were of      *
        *                      interest.                               *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The WQAL control block is modified to optionally allow setting
        the address (WQALWQLS or WQALWQL4) of a new qualification
        specification control block called the WQLS. The WQLSTYPE must
        be set to a value of 'DBSP' to identify that the qualification
        list is an array of DBID and PSID pairs. For the returned log
        records to include the ALTER COLUMN diagnostic log records the
        PSID should be the OBID of the tables within the table spaces.
        temp
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM90568
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DOCUMENTATION:
        PM90568 adds DBID/PSID or DBIB/OBID selection filtering to IFI
        306 log read via the DSNWLI READS call.

        A pointer is added to the WQAL interface control block and when
        non-zero points to a new WQLS control block for specification
        of the list of table space DBID and PSID or the table diagnostic
        log record DBID and OBID.

        The details are shown in the DSNDWQAL macro.
    COMMENTS:
1     CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNDQJ00  PM90568
       DSNDWQAL  PM90568
       DSNIDALC  PM90568
       DSNIDEFR  PM90568
       DSNIDLGR  PM90568
       DSNIDMPS  PM90568
       DSNIFLAR  PM90568
       DSNIFLRD  PM90568
       DSNILGRX  PM90568
       DSNILGSL  PM90568
       DSNILOGA  PM90568
       DSNIREDO  PM90568
       DSNIRSTR  PM90568
       DSNIUNDO  PM90568
       DSNJRE01  PM90568
       DSNJRM01  PM90568
       DSNJRM02  PM90568
       DSNJRM03  PM90568
       DSNJR001  PM90568
       DSNJR003  PM90568
       DSNJR006  PM90568
       DSNJR106  PM90568
       DSNUCLOG  PM90568
       DSNUGLGR  PM90568
       DSNURLOG  PM90568
       DSNWALRS  PM90568
       DSNWARDS  PM90568

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90568   DSNDQJ00 DSNDWQAL DSNIDALC DSNIDEFR DSNIDLGR DSNIDMPS
                 DSNIFLAR DSNIFLRD DSNILGRX DSNILGSL DSNILOGA DSNIREDO
                 DSNIRSTR DSNIUNDO DSNJRE01 DSNJRM01 DSNJRM02 DSNJRM03
                 DSNJR001 DSNJR003 DSNJR006 DSNJR106 DSNUCLOG DSNUGLGR
                 DSNURLOG DSNWALRS DSNWARDS

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIDALC
       DSNIDEFR
       DSNIDLGR
       DSNIDMPS
       DSNIFLAR
       DSNIFLRD
       DSNILGRX
       DSNILGSL
       DSNILOGA
       DSNIREDO
       DSNIRSTR
       DSNIUNDO
       DSNJRE01
       DSNJRM01
       DSNJRM02
       DSNJRM03
       DSNJR001
1      DSNJR003
       DSNJR006
       DSNJR106
       DSNUCLOG
       DSNUGLGR
       DSNURLOG
       DSNWALRS
       DSNWARDS

      MACROS
       DSNDQJ00
       DSNDWQAL

      LISTEND
 UK97013 COVER LETTER END


 UK97014 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM94528 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of SQL  *
        *                 recursive common table expressions (CTE).    *
        ****************************************************************
        * PROBLEM DESCRIPTION: An incorrect result set (the first row  *
        *                      is repeated) can be returned from a DB2 *
        *                      v9 bound static SQL package that        *
        *                      contains a CTE (common table            *
        *                      expression) when run on DB2 v10.        *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An incorrect result set (the first row is repeated) can be
        returned from a v9 bound static SQL package when run on v10 or
        v11.  The problem was reported for a package that includes a
        complex SQL statement that contains a recursive CTE with UNION
        ALL.  The problem is data dependent and can occur if one of the
        legs of the UNION ALL returns end of file (EOF) on the first
        fetch.

        The problem was reported with datasharing having both DB2 v9 and
        v10 members although this is not necessary.  The incorrect
        result is possible for any recursive CTE with UNION ALL that is
        contained in a v9 static SQL package that is bound on v9 and is
        now being run on v10 CM or NFM.

        The following CTE query is an example of a failing case. The top
        leg of the UNION ALL is the "seed leg" and the bottom leg is 
the
 
        "recursion leg'.

          WITH RPL (PART, SUBPART, QUANTITY) AS
            (SELECT ROOT.PART, ROOT.SUBPART, ROOT.QUANTITY
              FROM PARTLIST ROOT
                 WHERE ROOT.PART = "01"
             UNION ALL
             SELECT CHILD.PART, CHILD.SUBPART, CHILD.QUANTITY
1             FROM RPL PARENT, PARTLIST CHILD
                     WHERE PARENT.SUBPART = CHILD.PART)
          SELECT DISTINCT PART, SUBPART, QUANTITY
          FROM RPL
          ORDER BY PART, SUBPART, QUANTITY;


        An incorrect result (the first row is repeated) is returned from
        the application package if it was successfully bound and run on
        a v9 member and is now being run on a v10 member (w/o any
        rebind).

        The code in DB2 is modified to allow a v9 bound package as
        described to run without returning a result that includes a
        repeat of the first row.


        Additional Keywords: SQLUNIONALL SQLCTE SQLINCORROUT
                             DB2INCORR/K INCORROUT SQLINCORR

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM94528
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXRUN9  PM94528

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM94528   DSNXRUN9

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXRUN9

      LISTEND
 UK97014 COVER LETTER END


 UK97017 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM92205 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS RRSAF users.                *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C1 in DSNXEEZ when a DB2 SQL      *
        *                      COMMIT or SQL ROLLBACK has been issued  *
        *                      while the RRS Coordinator was not       *
        *                      available.                              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        During execution of a DB2 SQL COMMIT or SQL ROLLBACK DB2 will
        check with the RRS Coordinator to see if there are other
1       interested Resource Managers. If at the time the check
        occurs the RRS Coordinator has gone down, DB2 can be
        referencing residual RRS related structures.
        DB2 has been updated to check whether the z/OS RRS structures
        are still valid. If the structures are no longer valid, DB2 will
        assume z/OS RRS coordination is required with other Resource
        Managers and exit the SQL COMMIT or SQL ROLLBACK with no
        further action.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM92205
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXEEZ   PM92205

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM92205   DSNXEEZ

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXEEZ

      LISTEND
 UK97017 COVER LETTER END


 UK97020 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90970 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users.                   *
        ****************************************************************
        * PROBLEM DESCRIPTION: Preconditioning support for new         *
        *                      function.                               *
        ****************************************************************
        * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
        ****************************************************************
        This APAR, PM90970, is a preconditioning APAR for PM94353.
        This APAR, PM90970, is a preconditioning APAR for PM94353.

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM90970
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNGDAPT  PM90970
       DSNGDCDB  PM90970
       DSNIBCTD  PM90970
       DSNIDBAB  PM90970
       DSNIDBCA  PM90970
       DSNIDBCI  PM90970
1      DSNIDBCJ  PM90970
       DSNIDBCN  PM90970
       DSNIDBCO  PM90970
       DSNIDBCP  PM90970
       DSNIDBCQ  PM90970
       DSNIDBDF  PM90970
       DSNIDBLG  PM90970
       DSNIDBMF  PM90970
       DSNIDBSE  PM90970
       DSNIDRCT  PM90970
       DSNILSTS  PM90970
       DSNIOPPS  PM90970
       DSNISDB   PM90970
       DSNISPS   PM90970
       DSNISTFO  PM90970
       DSNTDCST  PM90970
       DSNTDDIS  PM90970
       DSNTDINQ  PM90970
       DSNTDMSG  PM90970
       DSNTDMST  PM90970
       DSNTDMUL  PM90970
       DSNTDSTP  PM90970
       DSNUECM4  PM90970
       DSNUGDBT  PM90970
       DSNUGDTC  PM90970
       DSNWDFDM  PM90970

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90970   DSNGDAPT DSNGDCDB DSNIBCTD DSNIDBAB DSNIDBCA DSNIDBCI
                 DSNIDBCJ DSNIDBCN DSNIDBCO DSNIDBCP DSNIDBCQ DSNIDBDF
                 DSNIDBLG DSNIDBMF DSNIDBSE DSNIDRCT DSNILSTS DSNIOPPS
                 DSNISDB  DSNISPS  DSNISTFO DSNTDCST DSNTDDIS DSNTDINQ
                 DSNTDMSG DSNTDMST DSNTDMUL DSNTDSTP DSNUECM4 DSNUGDBT
                 DSNUGDTC DSNWDFDM

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNGDAPT
       DSNGDCDB
       DSNIBCTD
       DSNIDBAB
       DSNIDBCA
       DSNIDBCI
       DSNIDBCJ
       DSNIDBCN
       DSNIDBCO
       DSNIDBCP
       DSNIDBCQ
       DSNIDBDF
       DSNIDBLG
       DSNIDBMF
       DSNIDBSE
       DSNIDRCT
       DSNILSTS
       DSNIOPPS
1      DSNISDB
       DSNISPS
       DSNISTFO
       DSNTDCST
       DSNTDDIS
       DSNTDINQ
       DSNTDMSG
       DSNTDMST
       DSNTDMUL
       DSNTDSTP
       DSNUECM4
       DSNUGDBT
       DSNUGDTC
       DSNWDFDM

      LISTEND
 UK97020 COVER LETTER END


 UK97022 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM94609 -
        ****************************************************************
        * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
        ****************************************************************
        * PROBLEM DESCRIPTION: Abend 04E-00D30014 DSNLTACC:000A        *
        *                      (GR3=0000C5E7_C3C1F1F0) for a non       *
        *                      DRDA exception condition event, such    *
        *                      as a CCSID translation not supported    *
        *                      condition.                              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The IFCID 299 trace event is designed to generate
        serviceability diagnostics, in the form of an abend dump, if
        a DRDA exception condition occurs. The 04E-00D30014
        DSNLTACC:000A abend dump is an indication of this
        serviceability trace event being enabled. However, in the
        case of CSECT DSNLTACC, this diagnostic abend dump may also
        be incorrectly generated in cases that don't technically
        qualify as an actual DRDA exception condition, such as when
        DB2 does not support character translation relative to the
        CCSID of the remote client environment.
        This inhibits the ability to run with this serviceability trace
        active because it essentially captures normal, or expected,
        events.

        Abend 04E-00D30014 DSNLTACC:000A is being qualified to
        consider an unsupported CCSID translation condition to be a
        normal event, which is not indicative of a DRDA exception
        condition.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM94609
    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
       DSNLTACC  PM94609

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM94609   DSNLTACC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNLTACC

      LISTEND
 UK97022 COVER LETTER END


 UK97025 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90171 -
        ****************************************************************
        * USERS AFFECTED: All DB2 11 and DB2 10 for z/OS users of      *
        *                 aggregate functions such as SELECT COUNT     *
        *                 DISTINCT on a VARCHAR NOT NULL column in a   *
        *                 table space or partition that is in Basic    *
        *                 Row Format (BRF)                             *
        ****************************************************************
        * PROBLEM DESCRIPTION: Incorrout possible during aggregate     *
        *                      functions such as SELECT COUNT DISTINCT *
        *                      when run on VARCHAR NOT NULL column in  *
        *                      BRF table space or partition            *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        For a basic row format (BRF) table space or partition, SELECT
        COUNT DISTINCT on a VARCHAR NOT NULL column returned fewer rows
        than expected.

        During the comparison of said column between rows, when a
        workfile was used for sorting, DB2 used a wrong length for
        comparison, off by 1 from what the comparison length should be.

        As a result, more rows were 'matching' each other and so fewer
        rows were distinct.
        DB2 code has been modified to make sure that COUNT DISTINCT on a
        VARCHAR NOT NULL column in a BRF table space or partition uses a
        correct column length when rows are compared to each other.

        Additional keywords: SQLINCORROUT SQLINCORR DB2INCORR/K
                             SQLSETFUNCTION SQLCOUNT
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM90171
    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      DSNISFRL  PM90171
       DSNISFS   PM90171
       DSNISFWL  PM90171
       DSNISFX2  PM90171

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90171   DSNISFRL DSNISFS  DSNISFWL DSNISFX2

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNISFRL
       DSNISFS
       DSNISFWL
       DSNISFX2

      LISTEND
 UK97025 COVER LETTER END


 UK97033 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM69341 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users and DB2 11 for     *
        *                 z/OS users of LOAD utility on a table which  *
        *                 has a foreign key constraint referencing a   *
        *                 primary key that contains INCLUDE COLUMNs.   *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00E20005 DSNSVBK +x'1AB6'    *
        *                      and MSGDSNU361I occurred when LOAD      *
        *                      data into a child table.                *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available.         *
        ****************************************************************
        A child table has a foreign key constraint that references a
        unique key of the parent table. When the primary key of the
        parent table contains INCLUDE COLUMNs, a LOAD on the child
        table may get DSNU361I -
          'FOREIGN KEY HAS NO PRIMARY KEY FOR RELATIONSHIP name',
        because LOAD did not take the INCLUDE COLUMN(s) into account
        when building the key for referential integrity checking.
        This caused a storage overlay to occur which resulted in the
        ABEND04E RC00E20005 at DSNSVBK OFFSET1AB6.
        LOAD utility code was modified to take the INCLUDE COLUMNs
        into account when building keys.

        Additional keywords: SMCOVERLAY DB2OVRLAY/K
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM69341
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNIKESR  PM69341
1      DSNURCRI  PM69341
       DSNURWIK  PM69341

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM69341   DSNIKESR DSNURCRI DSNURWIK

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIKESR
       DSNURCRI
       DSNURWIK

      LISTEND
 UK97033 COVER LETTER END


 UK97085 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM94111 -
        ****************************************************************
        * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
        *                 Specifically those with CICS PLT             *
        *                 applications with ACCOUNTREC(UOW).           *
        ****************************************************************
        * PROBLEM DESCRIPTION: Abend 04E-00D30014 DSNLTCCN:0010.       *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        DB2 10 for z/OS implemented support for Unicode DRDA traffic.
        This support is utilized only in New Function Mode and only if
        the remote server also indicates the necessary companion
        support.
        The user has a CICS PLT application with ACCOUNTREC(UOW) that
        accesses a remote server.  In this environment, CICS provides
        accounting information in a form that DB2 considers incomplete
        and does not expect.  If DB2 is operating in New Function Mode
        and the remote system being accessed supports Unicode DRDA
        traffic, then DB2 must translate the CICS accounting
        information into Unicode and in the process DB2 will detect the
        unexpected CICS accounting data in the form of the reported
        abend.

        DB2 has been changed to anticipate the incomplete CICS
        accounting data and ignore it in favor of generating a more
        appropriate value that can be sent to the remote server.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM94111
    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  PM94111

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1      PM94111   DSNLTCCN

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNLTCCN

      LISTEND
 UK97085 COVER LETTER END


 UK97087 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88540 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS, DB2 10 for z/OS, and     *
        *                 DB2 11 for z/OS users of RECOVER utility     *
        *                 on objects in the DB2 catalog and directory  *
        *                 to a prior point in time.                    *
        ****************************************************************
        * PROBLEM DESCRIPTION: GRECP and LPL status on an index in     *
        *                      the DB2 catalog prevents updates and    *
        *                      cannot be cleared in a disaster         *
        *                      recovery environment.                   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
          User created a user-defined, DB2 stogroup managed index on
        SYSIBM.SYSCOPY.  Due to a DB2 restart, this index was in
        GRECP state.  DSNDB06.SYSCOPY (DSNDB06.SYSTSCPY in DB2 11)
        was recovered to a prior point in time with TOLOGPOINT, all
        SYSCOPY indexes were rebuilt, and then DSNDB01.SYSLGRNX was
        recovered to a prior point in time and failed with
        DSNT501I  DSNIDBET RESOURCE UNAVAILABLE
                  REASON 00C900A1
                  TYPE 00000201
                  NAME DSNDB06 .user-defined-index-name
        and ABEND04E RC00C900A1
        because point-in-time recovery requires a row to be inserted
        into SYSCOPY but could not be due to the GRECP status of
        the index on SYSCOPY.

          Because this was in a disaster recovery environment, methods
        typically used to clear the GRECP status were not available
        or did not work, leaving the user unable to continue with
        any further point-in-time recoveries and no way to clear the
        GRECP status either.

          This happened in a data sharing environment but in a non-data
        sharing environment the same issue can be seen if the index on
        SYSCOPY is in LPL status.
          Code was changed in RECOVER utility so that if a table space
        is recovered to a prior point in time, as it sets the indexes
        to RBDP status, GRECP and LPL statuses, if they are found to be
        set, will be cleared, but only under the following conditions:
        1. The table space being recovered (and therefore its indexes)
1        is in the DB2 catalog or directory (i.e., databases DSNDB06 or
         DSNDB01), and,
        2. Either the index in question is partitioned, or the recovery
         of the table space is requested with DSNUM ALL.

        Additional keywords:  TOCOPY TOLASTCOPY TOLASTFULLCOPY TORBA
                              MSGDSNT501I
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88540
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUCARS  PM88540

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88540   DSNUCARS

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUCARS

      LISTEND
 UK97087 COVER LETTER END


 UK97099 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM93671 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS users                       *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNICLOS ERQUAL5007 *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        After calling the DB2 module that locates a PSCB (page set
        control block), the DB2 module that closes a page set checks the
        reason code even for a successful return code.  As the reason
        code is not set for RC 0, it could be any leftover value in the
        register.  As a result, a false alarm abend erqual5007 occurs in
        DSNICLOS.
        The code has been changed to not check the reason code when RC 0
        is returned from the module that locates the PSCB.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM93671
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNICLOS  PM93671
       DSNIOPNP  PM93671
       DSNIOPPS  PM93671
1      DSNIOPPZ  PM93671
       DSNPAVLR  PM93671
       DSNUKIFK  PM93671
       DSNUKNFK  PM93671

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM93671   DSNICLOS DSNIOPNP DSNIOPPS DSNIOPPZ DSNPAVLR DSNUKIFK
                 DSNUKNFK

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNICLOS
       DSNIOPNP
       DSNIOPPS
       DSNIOPPZ
       DSNPAVLR
       DSNUKIFK
       DSNUKNFK

      LISTEND
 UK97099 COVER LETTER END


 UK97104 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM93866 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of      *
        *                 time durations.                              *
        ****************************************************************
        * PROBLEM DESCRIPTION: DB2 returns an incorrect result         *
        *                      for datetime arithmetic where a time    *
        *                      duration is subtracted from a time.     *
        *                      The time duration must have the value   *
        *                      '24' for the hour and borrow from the   *
        *                      hour to calculate the result.           *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Datetime arithmetic may return an incorrect result if all of
        the following are true:

        1. The operation is subtraction.
        2. The operands are time and time duration.
        3. The time duration value for the hour is '24' (or any
           multiple of '24').
        4. The calculation involves borrowing from the hour for
           the minutes or seconds part of the calculation.

        The following is an example of the problem :

        SELECT TIME('00:00:01') - DECIMAL(240002,6,0)
        FROM SYSIBM.SYSDUMMY1;

        The value 01:59:59 is incorrectly returned.  The correct
1       result is 23:59:59.
        DB2 has been corrected to handle borrowing from the hour when
        the time duration has a multiple of 24.

        Additional keywords : INCORROUT   SQLTIME
                              SQLINCORR   DB2INCORR/K
                              SQLINCORROUT
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM93866
    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. 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
1       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  PM93866
       DSNXRDT9  PM93866

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM93866   DSNXRDTF DSNXRDT9

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXRDTF
       DSNXRDT9

      LISTEND
 UK97104 COVER LETTER END


 UK97105 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89866 -
        ****************************************************************
        * USERS AFFECTED: All data sharing DB2 users using LOBs.       *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C90101 in DSNODAL1         *
        *                      ERQUAL5003                              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When a Cancel is hit, DB2 abort processing may drive page
        recovery and rectify the LOB page read and write intent count.
        While rectifying the write intent count, for a GBP-dependent
        LOB object, its page may not be written out to the group buffer
        pool at commit and causes a LOB page regression.
        DB2 has been fixed to ensure that a LOB page for a GBP-dependent
        object is written out at commit during abort processing.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89866
    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  PM89866
       DSNB1RWI  PM89866

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89866   DSNB1RTR DSNB1RWI

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
1      DSNB1RTR
       DSNB1RWI

      LISTEND
 UK97105 COVER LETTER END


 UK97113 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM93358 -
        ****************************************************************
        * USERS AFFECTED: DB2 data sharing users.                      *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C200B0 in DSNB1REL.        *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The abend is the result of a timing window, during which one
        agent is releasing a page while another agent is refreshing
        the page in the page buffer.  If the table space or index is
        not LARGE format, and if the page on DASD has a non-zero value
        in the old PgLogID field, then the page number checking in
        DSNB1REL may fail, resulting in an ABEND04E RC00C200B0.

        DB2 has not used the PgLogID field since V3, so a non-zero
        value there for a non-LARGE pageset would indicate that the
        page hasn't been updated, and the pageset not rebuilt by a
        DB2 utility, since V3.
        DSNB1REL has been modified to ignore the old PgLogID field when
        validating the page number for a non-LARGE object.

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM93358
    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  PM93358

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM93358   DSNB1REL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNB1REL

      LISTEND
 UK97113 COVER LETTER END


 UK97115 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM91842 -
        ****************************************************************
1       * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
        ****************************************************************
        * PROBLEM DESCRIPTION: Potential hang or loop if invalid       *
        *                      data is received from a remote          *
        *                      partner.                                *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        A remote system provided invalid (DRDA formatted) data to DB2.
        Depending on the form of the invalid data and the uninitialized
        contents of an internal variable, DB2 may hang trying to
        receive more data, or loop indefinitely (in CSECT DSNLCKDS) if
        the DB2 IFCID 180 serviceability trace is enabled.

        DB2 has been changed to more effectively recognize invalid data
        being received from a remote partner.  This allows the DSNL032I
        message condition to be detected (instead of a hang or loop).
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM91842
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNLCKDS  PM91842

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM91842   DSNLCKDS

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNLCKDS

      LISTEND
 UK97115 COVER LETTER END


 UK97120 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM80405 -
        ****************************************************************
        * USERS AFFECTED: All users of DSNTSMFD in DB2 Version 10 for  *
        *                 z/OS are affected by this change.            *
        ****************************************************************
        * PROBLEM DESCRIPTION: Users of DSNTSMFD may observe the       *
        *                      following:                              *
        *                                                              *
        *                      (1) DSNTSMFD report shows incorrect     *
        *                          sizes for input and output records  *
        *                      (2) DSNTSMFD report shows invalid       *
        *                          compression percentages             *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        DSNTSMFD is a DB2-supplied sample application for decompressing
1       compressed DB2 SMF records.

        DSNTSMFD produces an end-of-job summary, which is written to
        the SYSPRINT DD:
          * Total SMF records read
          * Total DB2 records read
          * Total DB2 compressed records read
          * Total DB2 compressed records decompressed
          * Total non-DB2 records read
          * Aggregate size of all input records
          * Aggregate size of all input DB2 records
          * Aggregate size of all input DB2 compressed records
          * Aggregate size of all output DB2 records
          * Aggregate size of all DB2 expanded records
          * Aggregate size of all non-DB2 input records
          * Percentage saved using compression
          * Details of records by DB2 subsystem

        Currently, the variables to hold the aggregate sizes may
        wrap, and produce a summary report that contains invalid
        numbers for aggregate sizes and for percentage saved using
        compression.

        The output decompressed records themselves are not affected.

        DSNTSMFD is modified to use a larger variable to hold the
        aggregate size of records.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM80405
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        ***Action for PM80405 (V10)

        This PTF modifies the source code for DSNTSMFD (DB2 sample
        application for decompressing compressed DB2 SMF records).

        Applying the PTF updates only the DSNTSMFD source code.  The
        updates do not affect your current DSNTSMFD load module until
        you rebuild it as follows:
          (1) If you use DSNTSMFD as supplied by DB2,
              run job steps ASM and LKED of your customized copy
              of job DSNTEJDS to assemble and link-edit the load
              module for DSNTSMFD.
          (2) If you use a modified version of DSNTSMFD, redo your
              modifications and then run JOB steps ASM and LKED from
              your customized copy of job DSNTEJDS to assemble
              and link-edit the load module for DSNTSMFD.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNTSMFD  PM80405

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM80405   DSNTSMFD

1     THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MACROS
       DSNTSMFD

      LISTEND
 UK97120 COVER LETTER END


 UK97140 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM94871 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS users.                      *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E with a DB2 internal reason     *
        *                      code detected by a DB2 internal         *
        *                      checking routine.                       *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        A special DB2 internal checking routine detected an
        orphaned PRR and triggered this 04E abend with a
        DB2 internal reason code.
        Fixes made in DB2 to properly delete the PRR after retry.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM94871
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNICMT1  PM94871

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM94871   DSNICMT1

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNICMT1

      LISTEND
 UK97140 COVER LETTER END


 UK97146 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM73388 -
        ****************************************************************
        * USERS AFFECTED: DB2 9, 10 and 11 for z/OS users of ALTER     *
        *                 TABLESPACE MAXPARTITIONS                     *
        ****************************************************************
        * PROBLEM DESCRIPTION: Inconsistent package invalidation for   *
        *                      ALTER TABLESPACE MAXPARTITIONS          *
        ****************************************************************
1       * RECOMMENDATION:                                              *
        ****************************************************************
        DB2 9 for z/OS does not consistently invalidate plans and
        and packages on ALTER TABLESPACE MAXPARTITIONS. MAXPARTITIONS
        information is used internally at bind time for parallelism and
        failure to invalidate may result in incorrect output or other
        symptoms.

        DB2 10 and 11 for z/OS currently unnecessarily invalidate
        dependent packages even when the maximum number of partitions
        is not being increased on ALTER TABLESPACE MAXPARTITIONS.

        DB2 9, 10 and 11 for z/OS are being changed to only invalidate
        dependent plans and packages on ALTER TABLESPACE MAXPARTITIONS
        when the maximum number of partitions is being increased.

        This APAR does not fix existing packages that were bound prior
        to application of this APAR.
        DB2 has been fixed to invalidate dependent plans and packages
        on ALTER TABLESPACE MAXPARTITIONS in a consistent manner, and
        to only invalidate when the maximum number of partitions is
        being increased.

        ADDITIONAL KEYWORDS:
        SQLALTER

        HOLD text:

        PM73388 introduces the following changes to externals:

        DB2 9 for z/OS SQL Reference:
        ALTER TABLESPACE, Notes Section:
          Invalidation of plans and packages:
          ...
          <All of the plans and packages that refer to that table
          space are invalidated> when ALTER TABLESPACE with the
          MAXPARTITIONS clause is executed to increase the
          MAXPARTITIONS value.

        DB2 10 for z/OS SQL Reference:
        ALTER TABLESPACE, Notes Section:
          Invalidation of packages:
          All of the packages that refer to that table space are
          invalidated when any of the following conditions are true:
          ...
          - When increasing the MAXPARTITIONS attribute of a <table
            space>.

        DB2 11 for z/OS SQL Reference:
        ALTER TABLESPACE, Notes Section:
          Invalidation of packages:
          All of the packages that refer to that table space are
          invalidated when any of the following conditions are true:
          ...
          - When increasing the MAXPARTITIONS attribute of a <table
            space>.
1
        DB2 9, 10 and 11 for z/OS Application programming and SQL:
          New row added to Table 1. Changes that require packages to
          be rebound.

          Change made:
          ALTER TABLESPACE with MAXPARTITIONS to increase the maximum
          number of partitions

          Required Action:
          No action is required. DB2 automatically rebinds invalidated
          plans or packages.

        This is not the final version of changes. Information about
        these changes will be included in the Information Management
        Software for z/OS Solutions Information Center
        (http://publib.boulder.ibm.com/infocenter/imzic) at a later
        date.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM73388
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DOCUMENTATION:
        PM73388 introduces the following changes to externals:

        DB2 10 for z/OS SQL Reference:
        ALTER TABLESPACE, Notes Section:
          Invalidation of packages:
          All of the packages that refer to that table space are
          invalidated when any of the following conditions are true:
          ...
          - When increasing the MAXPARTITIONS attribute of a <table
            space>.

        DB2 10 for z/OS Application programming and SQL:
          New row added to Table 1. Changes that require packages to
          be rebound.

          Change made:
          ALTER TABLESPACE with MAXPARTITIONS to increase the maximum
          number of partitions

          Required Action:
          No action is required. DB2 automatically rebinds invalidated
          plans or packages.

        This is not the final version of changes. Information about
        these changes will be included in the Information Management
        Software for z/OS Solutions Information Center
        (http://publib.boulder.ibm.com/infocenter/imzic) at a later
        date.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXIATS  PM73388

1     CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM73388   DSNXIATS

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXIATS

      LISTEND
 UK97146 COVER LETTER END


 UK97149 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89047 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS, DB2 10 for z/OS and      *
        *                 DB2 11 for z/OS users of the LOAD utility.   *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C4 DSNUGSOR +x'2616' during a     *
        *                      RESTART(PHASE) of a LOAD utility in     *
        *                      the DISCARD phase.                      *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        A LOAD utility was restarted at the beginning of the DISCARD
        phase.  The utility abended with an ABENDS0C4 in DSNUGSOR
        OFFSET2616.  The abend occurred when residual information
        from the first invocation was used during RESTART processing.
        The LOAD utility has been modified to correct the aformentioned
        problem.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89047
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNURDER  PM89047
       DSNURDMA  PM89047

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89047   DSNURDER DSNURDMA

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNURDER
       DSNURDMA

      LISTEND
 UK97149 COVER LETTER END


 UK97156 COVER LETTER START
    PROBLEM DESCRIPTION(S):
1     PM92951 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 10 and 11 for z/OS.         *
        ****************************************************************
        * PROBLEM DESCRIPTION: An ABEND0C1 RC00000001 in CSECT         *
        *                      DSNTADL may occur following an          *
        *                      ABEND0C4 after an agent has been        *
        *                      cancelled during allocation resulting   *
        *                      in subsystem termination.               *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        If an agent is cancelled during early allocation there is a
        window where control structures have not been fully set up for
        use during deallocation. This may result in some type of
        ABEND0C4 followed by an ABEND0C1 and DB2 termination.
        Deallocation has been modified to not rely on possibly
        incomplete control structures.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM92951
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNTAAL   PM92951
       DSNTADL   PM92951
       DSNTLBAC  PM92951
       DSNXAAB   PM92951

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM92951   DSNTAAL  DSNTADL  DSNTLBAC DSNXAAB

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNTAAL
       DSNTADL
       DSNTLBAC
       DSNXAAB

      LISTEND
 UK97156 COVER LETTER END


 UK97158 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM93782 -
        ****************************************************************
        * USERS AFFECTED: All users of DSNTRIN, the installation and   *
        *                 configuration tool for DB2-supplied stored   *
        *                 procedures and user-defined functions (UDFs) *
        *                 in DB2 10 for z/OS and DB2 11 for z/OS, are  *
        *                 affected by this change.                     *
        ****************************************************************
        * PROBLEM DESCRIPTION: DSNTIJRV job step DSNTVFY ends with     *
1       *                      return code 12 and the following error  *
        *                      message:                                *
        *                        DSNT002I DSNTRIN RECEIVED AN          *
        *                          UNEXPECTED SQLCODE OF -811 FROM     *
        *                          THE 'SELECT COLUMN_SIZE FROM        *
        *                          SYSIBM.SQLTYPEINFO WHERE            *
        *                          TYPE_NAME = 'XML'                   *
        ****************************************************************
        * RECOMMENDATION: Apply the fixing PTF for this APAR.          *
        ****************************************************************
        DSNTRIN is a program called by job DSNTIJRT to install and
        configure DB2-supplied routines.  This includes validation and
        adjustment of various SQL objects that are used by the routines
        and that have been modified in the service stream or on a
        product version/release boundary.  Among these checks, DSNTRIN
        queries the SYSIBM.SQLTYPEINFO table (used by the DB2 metadata
        (DBMD) stored procedures) to see if certain rows contain the
        expected content.  Currently, this check can return an
        unexpected SQLCODE -811 (more than one row is returned to an
        embedded SELECT statement).  When this happens, DSNTRIN
        terminates with the symptoms noted in the PROBLEM DESCRIPTION
        section.

        In response, this APAR modifies DSNTRIN to prevent the failure.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM93782
    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@RIN   PM93782
       DSNTRIN   PM93782

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM93782   DSN@RIN  DSNTRIN

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNTRIN

      MACROS
       DSN@RIN

      LISTEND
 UK97158 COVER LETTER END


 UK97160 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM91421 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users who     *
        *                 cast a LOB data type to a CHAR/VARCHAR/      *
        *                 GRAPHIC/VARGRAPHIC/BINARY/VARBINARY data     *
1       *                 type.                                        *
        ****************************************************************
        * PROBLEM DESCRIPTION: An unexpected ABEND04E RC00E70005 at    *
        *                      DSNXRBND location M666 can occur when a *
        *                      data type conversion is being performed *
        *                      (a LOB is being converted to a          *
        *                      different data type) when an error      *
        *                      condition is reached.  Instead, DB2     *
        *                      should return a correct SQL error code. *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An unexpected ABEND04E RC00E70005 can occur at location DSNXRBND
        M666 when casting a LOB data type to a CHAR, VARCHAR, GRAPHIC,
        VARGRAPHIC, BINARY, or VARBINARY data type when an error
        condition is reached.  DB2 should return a correct SQLCODE
        instead.

        The following example can illustrate the problem.

        1. Create a Table with a LOB column and populate the table

           CREATE TABLE T1 (C1 CLOB(1K));

           INSERT INTO T1 VALUES(CLOB('TEST'));


        2. Execute a query which casts a LOB to a VARCHAR data type.

           SELECT CAST(C1 AS VARCHAR(3200)) FROM T1;


        During the conversion from CLOB to VARCHAR, if there is an error
        condition reached (e.g. a resource not available condition), DB2
        does not handle the error and externalize the error condition
        properly.  This eventually leads to the failure mentioned above.
        Instead, DB2 should issue an SQLCODE -904 in this case.
        The code in DB2 has been modified to prevent the unexpected
        abend by issuing the correct SQLCODE for the detected error.

        Additional Keywords: SQLLOB SQLCODE904 SQLCAST
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM91421
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXRBIN  PM91421
       DSNXRBI9  PM91421
       DSNXRDBC  PM91421
       DSNXRDB9  PM91421
       DSNXRSBC  PM91421
       DSNXRSB9  PM91421

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1      PM91421   DSNXRBIN DSNXRBI9 DSNXRDBC DSNXRDB9 DSNXRSBC DSNXRSB9

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXRBIN
       DSNXRBI9
       DSNXRDBC
       DSNXRDB9
       DSNXRSBC
       DSNXRSB9

      LISTEND
 UK97160 COVER LETTER END


 UK97162 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM83839 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS      *
        *                 utility users of UNLOAD from an image        *
        *                 copy created by COPYTOCOPY from a            *
        *                 FlashCopy image copy                         *
        ****************************************************************
        * PROBLEM DESCRIPTION: UNLOAD FROMCOPY of an image copy        *
        *                      created by COPYTOCOPY from a FlashCopy  *
        *                      image copy unloaded the incorrect       *
        *                      number of records                       *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        UNLOAD FROMCOPY of an image copy created by COPYTOCOPY from
        a FlashCopy image copy unloaded the wrong number of records.
        The FlashCopy image copy was taken after a mass delete
        followed by some inserts.  UNLOAD FROMCOPY when processing
        an image copy created from a FlashCopy did not correctly
        skip the mass delete pages and unloaded the records for
        mass delete pages.  This problem only occurs for segmented
        and universal table spaces (UTS).

        The same problem can also occur with FROMCOPYDDN and other
        mass delete operations on segmented and UTS table spaces
        such as TRUNCATE.

        Additional keywords: FlashCopy image copy (FCIC) FCIC
        UNLOAD FROMCOPY/FROMCOPYDDN has been changed to not unload mass
        deleted pages from image copies created with COPYTOCOPY from
        FlashCopy image copies.  The image copy created by COPYTOCOPY
        needs to be registered in SYSIBM.SYSCOPY.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM83839
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
1       The PTF for APAR PM83839 has modified CSECTs in both the
        DSNUT101 and DSNUTILA load modules, affecting the
        utility batch and DB2 DBM1 address spaces.  After the PTF has
        been applied, it will become active in the utility batch address
        space immediately upon job submission, while it will not take
        effect in the DB2 DBM1 address space until DB2 is stopped and
        started.

        The PTF does not have to be applied to all members in a data
        sharing environment simultaneously, and may be staged across
        each member.  However, until the fix is active in both the
        utility batch and DB2 DBM1 address spaces, the problem the PTF
        addresses will not be resolved.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUGUCA  PM83839
       DSNUULCA  PM83839
       DSNUULIA  PM83839
       DSNUULJA  PM83839
       DSNUUNLD  PM83839

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM83839   DSNUGUCA DSNUULCA DSNUULIA DSNUULJA DSNUUNLD

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUGUCA
       DSNUULCA
       DSNUULIA
       DSNUULJA
       DSNUUNLD

      LISTEND
 UK97162 COVER LETTER END


 UK97180 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89386 -
        ****************************************************************
        * USERS AFFECTED: Users who convert a simple table space to    *
        *                 partitioned by growth(PBG) table space.      *
        ****************************************************************
        * PROBLEM DESCRIPTION: Possible storage overlay                *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        A simple table space can be converted to PBG only if there is
        only one table in the table space.  If the simple table space
        had multiple tables in it, all the tables but one need to be
        dropped before is can be converted to PBG.  In this case,
        storage overlay may occur durring the REORG that converts the
        simple table space to PBG.
        DB2 is change to fix the problem.
    COMPONENT:  5740-XYR00-HDBAA10
1   APARS FIXED: PM89386
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNGDADP  PM89386
       DSNGDART  PM89386

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89386   DSNGDADP DSNGDART

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNGDADP
       DSNGDART

      LISTEND
 UK97180 COVER LETTER END


 UK97181 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM91726 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 10 for z/OS who use         *
        *                 common table expressions (CTEs) and          *
        *                 have subsystem parameters                    *
        *                 STARJOIN=ENABLE and EN_PJSJ=ON               *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C4 RC00000004 at DSNXGRTS +6BAC   *
        *                      can occur for a common table expression *
        *                      if pair-wise join access is chosen      *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        ABEND0C4 RC00000004 at DSNXGRTS +6BAC can occur for a CTE if
        pair-wise join access is chosen.  A noncorrelated CTE can
        be set up incorrectly for pair-wise join processing which would
        lead to an abend downsteam.

        Additional Keywords:
        SQLCTE SQLPAIRWISEJOIN ABEND0C4 RC04 OFFSET6BAC
        Code is added to correct the set-up so the abend does not occur.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM91726
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        A rebind is necessary for static applications to rebuild
        access paths based on changes in this APAR.

        PM88354 corrects a problem where a query meeting all of the
        following conditions could return incorrect output:
1       1. Has top-level UNION ALL;
        2. Each leg of the UNION ALL selects from the same single
           table;
        3. Each leg has the same columns in the SELECT list;
        4. There is no ORDER BY, GROUP BY, set function, or DISTINCT
           in any leg;
        5. Parallelism is not used; AND
        6. An index-on-expression is chosen for access to a table
           in one or more legs of the 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:
        See PM85237 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM85237 corrects an incorrect output problem that may occur
        when (1) sparse index access is used on a table, and (2) not
        all the eligible join predicates are used for the sparse index
        key.

        To make this fix effective for a static application, it must 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 PM84970:

        See PM84970 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM84970 corrects a problem of ABND04E RC00C90101 at DSNIWNRF
        ERQUAL 502C when a query contains a CREATE GLOBAL TEMPORARY
        TABLE in a correlated sub-select and the parent query block of
        the correlated sub-select 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 PM84151:

        See PM84151 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM84151 corrects a problem of an ABEND when an index on
        expression (IOE) is used against a range predicate in which the
        left-hand-side and right-hand-side have different string lengths
        and CCSIDs.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
1       affected by this change.
      DB2BIND:
        A rebind is necessary for static applications to rebuild
        access paths based on the changes in this APAR.

        APAR PM75619 corrects two problems. The first problem occurs
        on both V9 and V10.  A query may produce incorrect output
        when a UNICODE table joins to an EBCDIC view which is a
        UNION ALL, and at the same time, when index-on-expression
        (IOE) is used for that query.  The second problem occurs on V10
        only.  DB2 may not issue a REORG suggestion as it should.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        A rebind is necessary for static applications to rebuild
        access paths based on changes in this APAR.

        PM63095 corrects a problem of ABEND04E RC00C90101 in
        DSNIPSFI :5007 when executing an SQL statement containing
        a User Defined Function (UDF) with the DISALLOW PARALLEL
        parameter while parallelism is enabled.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOGP   PM91726

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM91726   DSNXOGP

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOGP

      LISTEND
 UK97181 COVER LETTER END


 UK97183 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89896 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of pureXML.        *
        ****************************************************************
        * PROBLEM DESCRIPTION: The is an enhancement that introduces   *
        *                      the DB2 subsystem parameter,            *
        *                      XML_RESTRICT_EMPTY_TAG, to control      *
        *                      whether DB2 should serialize an empty   *
        *                      XML element to <X></X> or <X/>. 
        *
 
1       ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The is an enhancement that introduces the DB2 subsystem
        parameter, XML_RESTRICT_EMPTY_TAG, to control whether DB2
        should serialize an empty XML element to <X></X> or 
<X/>.
 

        In DB2 8, the XML publishing function will serialize the empty
        XML element as <X></X>, assuming the element name is X. In 
DB2
 
        9, the XML publishing function has been changed to serialize the
        empty XML element to <X/>.

        Some DB2 applications might require the empty XML element to be
        serialized into a certain format. For example, the following
        expression requires the empty XML element to be serialized into
        <X></X>, so the REPLACE function can remove it.

        REPLACE(REPLACE(CAST(XML2CLOB(XMLAGG(
                             XMLELEMENT(NAME X, COL1)))
                        AS VARCHAR (200)),
                '<X>', ''),
        '</X>', '')

        When the empty XML element is serialized into <X/>, the query
        fails because the <X/> tag is not removed and breaks the
        subsequent operation.
        The DB2 subsystem parameter, XML_RESTRICT_EMPTY_TAG, is
        introduced to control which format the empty XML element should
        be serialized into.

        When the XML_RESTRICT_EMPTY_TAG is set to NO, then the empty
        XML element will be serialized into <X/>. This is default.
        When the XML_RESTRICT_EMPTY_TAG is set to YES, then the empty
        XML element will be serialized into <X></X>.

        Additional keywords: SQLXML XMLALL
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89896
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        This PTF adds a DB2 parameter, XML_RESTRICT_EMPTY_TAG, that can
        be specify whether DB2 will serialize an XML empty element using
        an empty element tag.

        XML provides two forms for denoting an empty element:
        - a short form of "<X/>" which is referred to as the 
empty
 
          element tag
        - a long form of "<X></X>" which is a 
start-element tag followed
 
          by an end-element tag.
        Across DB2 versions and depending on the context in which the
        empty XML element appears, DB2 sometimes generates 
"<X/>" and
 
        sometimes generates "<X></X>".

        The XML_RESTRICT_EMPTY_TAG subsystem parameter determines
1       whether DB2 will force the long form of the XML empty element.
        Valid settings are:
          * NO : Specifies that DB2 may serialize an empty XML element
                 as an empty-element tag or as a start-element followed
                 by an end-element.
                 ===> This is the default setting.
          * YES: Specifies that DB2 will not serialize an XML empty
                 element using an empty-element tag.  DB2 will serialize
                 an XML empty element using a start-element tag followed
                 by an end-element tag (i.e.
                 <emptyElement></emptyElement>).

        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 XML_RESTRICT_EMPTY_TAG=<x>,
              where <x> is NO or YES, to the invocation of the DSN6SPRM
              macro.  Make sure to add a continuation character in
              column 72 if needed.  If you omit adding
              XML_RESTRICT_EMPTY_TAG here, the value will be set to
              the default of NO when you assemble the DSNZPxxx module.

            * Run the first two steps of the DSNTIJUZ job you modified.

            * After the job completes, you must either use the -SET
              SYSPARM command or stop and restart DB2 for the change to
              take effect.

        ----------------------------------------------------------------
        (3) Update private copies of the DSNTIDxx CLIST input member
        ==> This action is required for all customers
1
             This PTF adds an entry for XML_RESTRICT_EMPTY_TAG 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:

        XML_RESTRICT_EMPTY_TAG CHAR  M  NO          YES           <x>

             Change <x> to the value you specified for
             XML_RESTRICT_EMPTY_TAG in step (2), above.

        ----------------------------------------------------------------
        (4) Update the package for DSNTXAZP
        ==> This action is required for all customers who use DSNTXAZP
            to update DB2 CLIST input (DSNTIDXX) members:

            Submit a job that contains the following BIND statement:

                BIND PACKAGE(DSNTXAZP) MEMBER(DSNTXAZP) -
                     ACTION(ADD) ENCODING(EBCDIC) -
                     LIBRARY('prefix.SDSNDBRM')

            where <prefix> is the high-level qualifier for the
            DB2 subsystem target libraries.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSN@XAZP  PM89896
       DSNDQWPZ  PM89896
       DSNDSPRM  PM89896
       DSNNOSCO  PM89896
       DSNNOSER  PM89896
       DSNTIDXA  PM89896
       DSNTIDXB  PM89896
       DSNTIJUZ  PM89896
       DSNTINST  PM89896
       DSNTXAZP  PM89896
       DSNWZIFA  PM89896
       DSN6SPRM  PM89896

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89896   DSN@XAZP DSNDQWPZ DSNDSPRM DSNNOSCO DSNNOSER DSNTIDXA
                 DSNTIDXB DSNTIJUZ DSNTINST DSNTXAZP DSNWZIFA DSN6SPRM

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNNOSCO
       DSNNOSER
       DSNTXAZP
       DSNWZIFA

      MACROS
       DSN@XAZP
       DSNDQWPZ
       DSNDSPRM
1      DSNTIDXA
       DSNTIDXB
       DSNTIJUZ
       DSNTINST
       DSN6SPRM

      LISTEND
 UK97183 COVER LETTER END


 UK97198 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89899 -
        ****************************************************************
        * USERS AFFECTED: Users of DB2 for z/OS IFCIDs 108,109,110,    *
        *                 111,112 and/or 177.                          *
        ****************************************************************
        * PROBLEM DESCRIPTION: When capturing trace records for IFCIDs *
        *                      108,109,110,111,112 and/or 177, the     *
        *                      length of the record may be longer than *
        *                      needed. Extraneous bytes of '00'x may   *
        *                      exist at the end of the record.         *
        *                                                              *
        *                      Furthermore, for IFCID 110, the length  *
        *                      of the record may be too short when any *
        *                      one of the following conditions exists: *
        *                                                              *
        *                       - Location is longer than 16 bytes     *
        *                       - Collection ID is longer than 18      *
        *                         bytes                                *
        *                       - Package name is longer than 18 bytes *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When capturing trace records for IFCIDs 108,109,110,111,112
        and/or 177, the length of the record may be longer than needed.
        Extraneous bytes of '00'x may exist at the end of the record.
        These bytes represent the space for long names if they exist.

        Furthermore, for IFCID 110, the length of the record may be too
        short when any one of the following conditions exists:

         - Location is longer than 16 bytes
         - Collection ID is longer than 18 bytes
         - Package name is longer than 18 bytes

        In this scenario, the record will contain offsets that point to
        the long names. However, the long names may not be printed out
        at the specified offsets.

        The incorrectly formatted trace records were caused by program
        error.

        Additional keywords:
        IFCID108 IFCID109 IFCID110 IFCID111 IFCID112 IFCID177

1       DB2 code is now changed to handle long names correctly and
        output the appropriate length for the record.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89899
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNTAAL   PM89899
       DSNTBBP   PM89899
       DSNTBBP2  PM89899
       DSNTBFR   PM89899
       DSNTBFR2  PM89899
       DSNXEAAL  PM89899

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89899   DSNTAAL  DSNTBBP  DSNTBBP2 DSNTBFR  DSNTBFR2 DSNXEAAL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNTAAL
       DSNTBBP
       DSNTBBP2
       DSNTBFR
       DSNTBFR2
       DSNXEAAL

      LISTEND
 UK97198 COVER LETTER END


 UK97204 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM87740 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 and 10 for z/OS users of RLF       *
        ****************************************************************
        * PROBLEM DESCRIPTION:  This APAR adds                         *
        *                              RLF serviceability traces.      *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        This APAR adds RLF serviceability traces for predictive
        governing and reactive governing.
        IFCID 397 and 398 are enabled to support RLF predictive
        governing and reactive governing respectively.

        Additional keywords: IFCID397 IFCID398
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM87740
    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
       DSNB1GET  PM87740
       DSNDQWHS  PM87740
       DSNDQW05  PM87740
       DSNWVINT  PM87740
       DSNXEDP   PM87740
       DSNXEDSC  PM87740
       DSNXEDS1  PM87740
       DSNXEET   PM87740
       DSNXERD   PM87740
       DSNXERT   PM87740
       DSNXERT2  PM87740
       DSNXRSTP  PM87740
       DSNXRSTS  PM87740
       DSNXRTSC  PM87740
       DSNXRTSK  PM87740
       DSNXRTSS  PM87740
       DSNXSBUC  PM87740
       DSNXSFML  PM87740
       DSNXSFRT  PM87740
       DSNXSIFF  PM87740
       DSNXSIFG  PM87740
       DSNXSIND  PM87740
       DSNXSINE  PM87740
       DSNXSING  PM87740
       DSNXSMIG  PM87740
       DSNXSMRD  PM87740
       DSNXSMRG  PM87740
       DSNXSMRL  PM87740
       DSNXSORM  PM87740
       DSNXSRCY  PM87740
       DSNXSRID  PM87740
       DSNXSTSD  PM87740
       DSNXSTSG  PM87740
       DSNXSZK   PM87740
       DSNXXMRD  PM87740
       DSNXXRID  PM87740

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM87740   DSNB1GET DSNDQWHS DSNDQW05 DSNWVINT DSNXEDP  DSNXEDSC
                 DSNXEDS1 DSNXEET  DSNXERD  DSNXERT  DSNXERT2 DSNXRSTP
                 DSNXRSTS DSNXRTSC DSNXRTSK DSNXRTSS DSNXSBUC DSNXSFML
                 DSNXSFRT DSNXSIFF DSNXSIFG DSNXSIND DSNXSINE DSNXSING
                 DSNXSMIG DSNXSMRD DSNXSMRG DSNXSMRL DSNXSORM DSNXSRCY
                 DSNXSRID DSNXSTSD DSNXSTSG DSNXSZK  DSNXXMRD DSNXXRID

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNB1GET
       DSNWVINT
       DSNXEDP
       DSNXEDSC
       DSNXEDS1
       DSNXEET
       DSNXERD
1      DSNXERT
       DSNXERT2
       DSNXRSTP
       DSNXRSTS
       DSNXRTSC
       DSNXRTSK
       DSNXRTSS
       DSNXSBUC
       DSNXSFML
       DSNXSFRT
       DSNXSIFF
       DSNXSIFG
       DSNXSIND
       DSNXSINE
       DSNXSING
       DSNXSMIG
       DSNXSMRD
       DSNXSMRG
       DSNXSMRL
       DSNXSORM
       DSNXSRCY
       DSNXSRID
       DSNXSTSD
       DSNXSTSG
       DSNXSZK
       DSNXXMRD
       DSNXXRID

      MACROS
       DSNDQWHS
       DSNDQW05

      LISTEND
 UK97204 COVER LETTER END


 UK97227 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM91172 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 and 11 for z/OS users of          *
        *                 OMNIFIND functions.                          *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C4 RC04 at DSNXRFN +268A may      *
        *                      occur when executing a query which uses *
        *                      an OMNIFIND function and for which a    *
        *                      hybrid join plan is chosen.             *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        ABEND0C4 RC04 at DSNXRFN +268A may occur when executing a query
        which satisfies all of the following conditions:

        1. The query uses an OMNIFIND function. For example,

           SELECT *
1          FROM T1, T2
           WHERE CONTAINS(T1.C1, 'TEST') = 1
           AND T1.C2 = T2.C2;

        2. A hybrid join plan is chosen and neither sort composite nor
        sort new table is chosen for the hybrid join (METHOD=4,
        SORTC_JOIN='N' and SORTN_JOIN='N');

        3. The table with the OMNIFIND function is accessed before the
        hybrid join plan and DB2 decides to execute the OMNIFIND
        function in table function mode.

        4. If there is any plan between the plan to access the table
        with the OMNIFIND function and the hybrid join plan, that plan
        must be a nested loop join plan without sort composite or sort
        new table (METHOD=1, SORTC_JOIN='N' and SORTN_JOIN='N').

        Additional Keywords:
        ABEND0C4 RC04 at DSNXRFN OFFSET268A SQLHYBRID SQLHYBRIDJOIN
        HYBRIDJOIN OMNIFIND TEXTSEARCH
        Code has been modified to add a sort composite to the hybrid
        join plan for the cases described as above.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM91172
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM91172:

        A rebind is necessary for static applications to rebuild the
        access paths based on the changes in this APAR.

        PM91172 corrects a problem that ABEND0C4 RC04 at DSNXRFN +268A
        may occur when executing a query which uses an OMNIFIND
        function and for which a hybrid join plan 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.
      DB2BIND:
        ***Action for PM81000:

        A rebind is necessary for static applications to rebuild
        access paths based on changes in this APAR.

        PM81000 corrects a problem of inaccurately estimated I/O and
        CPU of a parent query block table in hybrid join when
        parallelism is enabled.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
    COMMENTS:
1     CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOCSH  PM91172

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM91172   DSNXOCSH

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOCSH

      LISTEND
 UK97227 COVER LETTER END


 UK97229 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88455 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS      *
        *                 users of point-in-time (PIT) recovery.       *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C90101 at DSNKPGCM:5008    *
        *                      and RC00E40333 or other unpredictable   *
        *                      results during a PIT RECOVER on an      *
        *                      index to a time point before a REORG    *
        *                      which materialized pending ALTERs on    *
        *                      its table space.                        *
        *                                                              *
        *                      MSGDSNU809I issued during a CHECK DATA  *
        *                      on a table with LOB columns after a PIT *
        *                      RECOVER on its base table space and LOB *
        *                      table space to a time point before a    *
        *                      MODIFY RECOVERY utility.                *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available.         *
        ****************************************************************
        This APAR addresses two problems.

        A REORG TABLESPACE utility ran on a table space and materialized
        pending ALTERs on it.  Then a PIT RECOVER utility on its index
        to a time point before this REORG abended with ABEND04E
        RC00C90101 at DSNKPGCM ERQUAL5008 and RC00E40333.

        A PIT RECOVER utility ran on a partitioned table space with LOB
        columns to a time point which was before a MODIFY RECOVERY
        utility was executed on some of its LOB table spaces.  Because
        the MODIFY RECOVERY deleted the information needed for the
        recovery, the RECOVER led to data inconsistency between the base
        table and the LOB, which was detected by a subsequent CHECK DATA
        and the message DSNU809I - TABLE=table_name COLUMN=column_name
        IS MISSING IN INDEX index_name ROWID=rowid VERSION=version was
        issued.

        In both cases the point-in-time recovery caused the problems,
        and should not have been allowed.
1
        Additional keywords: TORBA, TOLRSN, TOLOGPOINT, TOCOPY,
                             TOLASTCOPY, TOLASTFULLCOPY
        RECOVER utility code was modified so that if a recovery is
        attempted on an index to a point in time prior to a REORG
        utility which materialized pending ALTERs on its underlying
        table space, or, if a recovery is attempted to a point in time
        prior to a MODIFY RECOVERY utility, the result will be
        MSGDSNU556I - RECOVER CANNOT PROCEED FOR ... BECAUSE A
        SYSIBM.SYSCOPY RECORD HAS BEEN ENCOUNTERED WHICH HAS ...,
        and the recovery of that object will fail.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88455
    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  PM88455

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88455   DSNUCASA

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUCASA

      LISTEND
 UK97229 COVER LETTER END


 UK97231 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM95745 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 for zOS.                    *
        ****************************************************************
        * PROBLEM DESCRIPTION: Incorrect abend regs from DSN3ABND      *
        *                      for RARQ sequence error.                *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        DSN3ABND loses the code register when preparing to issue
        an ABEND04E RC00E50063 for a RARQ sequence error.  This
        results in an ABEND with an invalid ABEND code and reason
        code.  The abend can occur when there is a sequence error in
        the Identify, Signon, Create Thread process.  An example is
        when two consecutive Create Thread requests are issued.  The
        ABEND04E RC00E50063 should be retried by the recovery routine
        in DSNAPRHX, and a FRB RC256 RC00E50063 returned back to the
        requestor for the RARQ sequence error.
        Register usage in DSN3ABND has been corrected.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM95745
    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
       DSN3ABND  PM95745

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM95745   DSN3ABND

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSN3ABND

      LISTEND
 UK97231 COVER LETTER END


 UK97236 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM92289 -
        ****************************************************************
        * USERS AFFECTED: All DB2 users of the RESTORE SYSTEM Utility. *
        ****************************************************************
        * PROBLEM DESCRIPTION: (1) ABEND04E RC00E2000C DSNSVSVB DURING *
        *                      RESTORE SYSTEM LOG APPLY.               *
        *                      (2) ABEND0C4 RC00C90101 DSNIRSTR+5A52   *
        *                      DURING RESTORE SYSTEM LOG APPLY.        *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        During RESTORE SYSTEM log apply, it is possible that all the
        available storage in the local storage pool (CT64BSTP) may not
        be enough to hold the information about all the objects involved
        in data recovery. When the local storage pool's maximum capacity
        is reached, it results in Abend04E with reason code RC00E2000C.
        This results in DB2 abnormally terminated. In order to avoid,
        this storage exhausted condition during Restore System log apply
        phase, Data Manager (DM) log apply routine, will temporarily
        increase the storage limit for storage pool CT64BSTP so that
        restore system can complete processing all the log record
        without interruption.
        Restore System utility logic is modified to avoid storage
        exhausted condition during log apply phase.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM92289
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNIRSTR  PM92289

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM92289   DSNIRSTR

1     THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIRSTR

      LISTEND
 UK97236 COVER LETTER END


 UK97238 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM94803 -
        ****************************************************************
        * USERS AFFECTED: All DB2 users.                               *
        ****************************************************************
        * PROBLEM DESCRIPTION: INCOMPLETE CORRELATION-ID INFORMATION   *
        *                      IN MESSAGE DSNT376I FOR FAST LOG APPLY  *
        *                      TASK.                                   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        During DB2 restart or Logical Page List (LPL) or Group Recovery
        (GRECP), when Fast Log Apply (FLA) is active and if log apply
        routine time out on IRLM lock request, it is possible that
        correlation -ID in the message DSNT376I may not contain a
        complete information. This is because when the Service Resource
        Block (SRB) is created for each FLA task, does not properly
        initialize CIDFNAME which is used in constructing correlation-ID
        for newly created SRB. The FLA logic is corrected so that each
        FLA task will have complete correlation-ID information.
        DB2 restart and/or LPL/GRECP recovery logic is corrected so that
        DSNT376I message will contain complete correlation-ID
        information.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM94803
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNIGTSK  PM94803

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM94803   DSNIGTSK

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIGTSK

      LISTEND
 UK97238 COVER LETTER END


 UK97243 COVER LETTER START
    PROBLEM DESCRIPTION(S):
1     PM82425 -
        ****************************************************************
        * USERS AFFECTED: All DB2 users of real time statistics for    *
        *                 last used information in SYSPACKAGE          *
        ****************************************************************
        * PROBLEM DESCRIPTION: Customer may receive an incomplete      *
        *                      message,                                *
        *                                                              *
        *                      DSNT500I -DB2E DSNGERTS RESOURCE        *
        *                                UNAVAILABLE                   *
        *                                REASON 00C90306               *
        *                                TYPE 00000000                 *
        *                                NAME                          *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        DB2 maintains a list of real time statistics (RTS)
        control blocks to keep track of package execution. The RTS
        service task periodically externalizes the last used
        information to the SYSPACKAGE table. When the number of
        RTS control blocks is more than the DB2 system can handle,
        DB2 purges the exceeding RTS control blocks and the above
        incorrect message is issused.
        DB2 has been changed to return the correct message.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM82425
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNGEINT  PM82425
       DSNGEPLC  PM82425
       DSNGERTS  PM82425
       DSNIRTST  PM82425

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM82425   DSNGEINT DSNGEPLC DSNGERTS DSNIRTST

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNGEINT
       DSNGEPLC
       DSNGERTS
       DSNIRTST

      LISTEND
 UK97243 COVER LETTER END


 UK97245 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90487 -
        ****************************************************************
        * USERS AFFECTED: All DB2 user of package bound in V10.        *
1       ****************************************************************
        * PROBLEM DESCRIPTION: Running a package may receive ABEND04E  *
        *                      RC00E2000F at DSNWVZSA.DSNSVSFB+0858.   *
        *                      There could be other unpredictable      *
        *                      results may occur.                      *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When executing a package, an internal data structure is
        allocated and is used for the package execution. If
        an object referenced by the package is altered or
        dropped/re-created, the package is marked as invalid
        and the internal data structure is freed as part of
        invalidation process. Re-executing the same package
        could access the freed data structure.
        DB2 has been changed to not free the internal data
        structure if there is an active package execution
        until the package execution is committed or the thread
        is terminated.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM90487
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNGEPDL  PM90487

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90487   DSNGEPDL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNGEPDL

      LISTEND
 UK97245 COVER LETTER END


 UK97263 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90310 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of CHECK DATA      *
        *                 AUXERROR INVALIDATE on directory objects     *
        ****************************************************************
        * PROBLEM DESCRIPTION: CHECK DATA AUXERROR INVALIDATE was      *
        *                      ignored for LOB columns for directory   *
        *                      objects.                                *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        CHECK DATA TABLESPACE DSNDB01.SPT01 AUXERROR INVALIDATE
        issued multiple MSGDSNU809I indicating missing AUX index entries
        but was not invalidating the LOB columns.  CHECK DATA SHRLEVEL
1       REFERENCE AUXERROR INVALIDATE should invalidate LOB columns
        for directory objects.  CHECK DATA SHRLEVEL CHANGE AUXERROR
        INVALIDATE should generate REPAIR statements for invalid LOB
        columns for directory objects.
        CHECK DATA has been modified to honor AUXERROR INVALIDATE
        for directory objects.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM90310
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      ACTION:
        The PTF for APAR PM90310 has modified CSECTs in both the
        DSNUT101 and DSNUTILA load modules, affecting the utility
        batch and DB2 DBM1 address spaces.  After the PTF has been
        applied, it will become active in the utility batch address
        space immediately upon job submission, while it will not take
        effect in the DB2 DBM1 address space until DB2 is stopped and
        started.

        The PTF does not have to be applied to all members in a data
        sharing environment simultaneously, and may be staged across
        each member.  However, until the fix is active in both the
        utility batch and DB2 DBM1 address spaces, the problem the PTF
        addresses will not be resolved.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUKERK  PM90310
       DSNUKRDN  PM90310
       DSNUKRDY  PM90310

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90310   DSNUKERK DSNUKRDN DSNUKRDY

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUKERK
       DSNUKRDN
       DSNUKRDY

      LISTEND
 UK97263 COVER LETTER END


 UK97269 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM91862 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS      *
        *                 users of tracker site.                       *
        ****************************************************************
        * PROBLEM DESCRIPTION: MSGDSNT501I RC00C900AC DSNDB06.SYSRTSTS *
        *                      during shutdown of tracker site.        *
        *                      Real-Time Statistics (RTS) service task *
        *                      should not be started on a tracker site *
1       ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        MSGDSNT501I RESOURCE UNAVAILABLE REASON RC00C900AC RTS
        occurred during the shutdown of a tracker site when attempting
        to externalize RTS to SYSIBM.SYSTABLESPACESTATS.  RTS should
        not be started on a tracker site.
        Code has been modified to correct the aforementioned problem.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM91862
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNIRTST  PM91862

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM91862   DSNIRTST

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIRTST

      LISTEND
 UK97269 COVER LETTER END


 UK97275 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM91455 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of IN predicate    *
        *                 with full outer join                         *
        ****************************************************************
        * PROBLEM DESCRIPTION: An incorrect result NRF can be returned *
        *                      for an SQL statement that contains full *
        *                      outer join within an IN predicate.      *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        DB2 may return an incorrect result set for a query that contains
        a full outer join within an IN predicate or other set comparison
        predicate. The problem occurs because DB2 does not correctly
        clean up the internal structures for the full outer join after
        each execution of the set comparison predicate.

        The following example illustrates how this problem can occur.

        1. Create Tables and insert some rows.

         CREATE TABLE T1 (C1 INT, C2 INT, C3 INT);
         CREATE TABLE T2 (C1 INT, C2 INT, C3 INT);
         CREATE TABLE T3 (C1 INT, C2 INT, C3 INT);
         INSERT INTO T1 VALUES (1,1,1) ;
1        INSERT INTO T1 VALUES (2,2,2) ;
         INSERT INTO T1 VALUES (3,3,3) ;
         INSERT INTO T2 VALUES (1,5,1) ;
         INSERT INTO T2 VALUES (2,2,2) ;
         INSERT INTO T2 VALUES (3,6,3) ;
         INSERT INTO T3 VALUES (1,1,0) ;
         INSERT INTO T3 VALUES (2,2,0) ;
         INSERT INTO T3 VALUES (3,3,0) ;

        2. Execute the following query.

         EXEC SQL SELECT COUNT(*) FROM T3 C
          WHERE C1 IN (SELECT  A.C1  FROM T1 A
                       FULL OUTER JOIN T2 B ON A.C2 = B.C2
                       WHERE B.C3 IS NULL AND C.C3 = 0);

        The query can return 1 but it should return 2 for the count.

        DB2 code is modified to clean up the internal structures
        correctly.

        Additional Keywords: SQLINCORR SQLINCORROUT INCORROUT SQLFULL
                             DB2INCORR/K SQLINSUBQ SQLFULLJOIN
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM91455
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXRSC2  PM91455
       DSNXRS29  PM91455

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM91455   DSNXRSC2 DSNXRS29

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXRSC2
       DSNXRS29

      LISTEND
 UK97275 COVER LETTER END


 UK97283 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM92941 -
        ****************************************************************
        * USERS AFFECTED: DB2 z/OS users of stored procedures          *
        *                 and User Defined Functions (UDFs).           *
        ****************************************************************
        * PROBLEM DESCRIPTION: After forcing down a stored procedure   *
        *                      application, the job hung waiting for   *
        *                      active distributed stored procedure     *
1       *                      to finish. "END OF MEMORY RESOURCE      *
        *                      MANAGER HANG DETECTED" and then DB2     *
        *                      abended with ABEND30D RC00F30411.       *
        *                      DSNX9EMR                                *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        After forcing down the application, DB2 recovery is expected
        to issue CALLRTM to terminate the threads. In this case,
        there are more than one stored procedure threads that need
        to be terminated. DB2 issued the CALLRTM against the first
        one, but not for the rest. This is because DB2 recovery
        incorrectly check the requests that need to be terminated and
        therefore skipped the CALLRTM for the stored procedures that
        are still in the queue. This results in the hang situation.
        Finally, DB2 issued ABEND30D and retried 10 times and then
        went down with RC00F30411.
        DB2 recovery code has been fixed to issue CALLRTM to all
        stored procedure requests that need to be terminated in
        this situation.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM92941
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNX9MON  PM92941

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM92941   DSNX9MON

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNX9MON

      LISTEND
 UK97283 COVER LETTER END


 UK97294 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM92953 -
        ****************************************************************
        * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
        *                 Specifically where DB2 is configured with    *
        *                 DDF THREADS=INACTIVE specified               *
        *                 (DSN6FAC CMTSTAT INACTIVE).                  *
        ****************************************************************
        * PROBLEM DESCRIPTION: IFCID 3 accounting record reflects      *
        *                      a QWACABRT count when the application   *
        *                      did not perform a rollback or suffer    *
        *                      any errors.                             *
        ****************************************************************
        * RECOMMENDATION:                                              *
1       ****************************************************************
        When a remote application commits and terminates its connection
        to a DB2 for z/OS server, DB2 (DDF) Inactive Thread support
        processing will pool the associated DBAT so that it can be used
        to service other connections.
        During the process of pooling the DBAT, DB2 internally drives
        abort processing in order to clean up any residual resources
        that may be left as a result of the application behavior.  This
        is done in order to eliminate any resources that might
        otherwise be incorrectly inherited by a remote application that
        is subsequently serviced by the pooled DBAT.  However, DB2 will
        drive this abort processing before ending the accounting
        interval for the prior transaction.  As a result, the IFCID 3
        accounting record will reflect an abort condition (QWACABRT)
        even though the remote application did not execute an abort or
        suffer any errors that might lead to an abort.

        After servicing a connection termination event from a remote
        application, DB2 has been changed to end the transaction
        accounting interval before driving abort processing in
        preparation for pooling the DBAT.
        Note: Users may notice an increase in IFCID 3 accounting
          records after this change as some transactions are now
          being correctly reflected where they were not before.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM92953
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNLQCTL  PM92953

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM92953   DSNLQCTL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNLQCTL

      LISTEND
 UK97294 COVER LETTER END


 UK97296 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM93676 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of the  *
        *                 EXTENDEDINDICATOR bind option.               *
        ****************************************************************
        * PROBLEM DESCRIPTION: An ABEND04E rc00C90101 can occur at     *
        *                      location DSNINUKY 5001 for an SQL       *
        *                      UPDATE statement in an application that *
        *                      tries to update a key column in a hash  *
1       *                      unique index when using the             *
        *                      EXTENDEDINDICATOR bind option.          *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An ABEND04E rc00C90101 can occur at location DSNIDM DSNINUKY
        5001 (ERQUAL5001) when an UPDATE statement in an application
        tries to update a key column in a hash unique index when using
        the EXTENDEDINDICATOR bind option.

        The failure occurs because DB2 does not handle a deferred
        SQLCODE -151 properly. Instead, an SQLCODE151 should be returned
        to the application. This failure can occur for both a local or
        a distributed application.

        The following example illustrates a failing case.

        STEP 1. Create a Table with a HASH Index.

          CREATE TABLE TEST_02
           (RECID              BIGINT NOT NULL,
            SUBSEQNO           SMALLINT NOT NULL,
            RECDATE            DATE NOT NULL,
            RECTYPE            CHAR(2) FOR MIXED DATA WITH DEFAULT NULL,
            ...
                              )
             IN DBTEST.TSTEST
             ORGANIZE BY HASH UNIQUE (RECDATE,
                                      RECID,
                                      SUBSEQNO)
             HASH SPACE 16M
             PARTITION BY SIZE
             AUDIT NONE
             DATA CAPTURE NONE
             CCSID      UNICODE
             NOT VOLATILE
             APPEND NO  ;


        STEP 2. Populate the Table.

          INSERT INTO  TEST_02
           VALUES (0001, 0001, CURRENT DATE, 'BB', ...);


        STEP 3. Prepare the following application which contains an
                UPDATE statement to update a HASH INDEX KEY column.

          Set IND2 to a value of 0.

          MOVE  1 to HV1.
          EXEC SQL
            SET :HV2 = '07/10/2013'
          END-EXEC


1         EXEC SQL UPDATE TEST_02 SET RECDATE=:HV2:IND2
                        WHERE RECID = :HV1
          END-EXEC.


        STEP 4. Bind the application using the EXTENDEDINDICATOR bind
                option.

          BIND PACKAGE(PKGSAMP) VALIDATE(RUN) ACTION(REP) -
               MEMBER(PROGA) RELEASE(COMMIT) EXTENDEDINDICATOR(YES)
          BIND PLAN(PLNSAMP) ACTION(REP)   -
               PKLIST(*.PKGSAMP.PROGA) VALIDATE(RUN) -
               RELEASE(COMMIT)


        STEP 5. Execute the package. The abend above should occur.

          RUN  PLAN(PLNSAMP) PROGRAM(PROGA)


        Alternatively, the problem can also occur if an index is altered
        to be a hash index before some update operation.

        Please note:
        The same failure can occur whether using an indicator variable
        for the host variable being updated or not, or whether the
        application is bound to run locally or via a distributed flow.
        An SQLCODE -151 is expected instead of the abend.


        Additionally, this apar corrects a problem regarding an
        SQLCODE798 not being returned to the application when using the
        EXTENDEDINDICATOR bind option when trying to insert into a
        GENERATED ALWAYS column.  Instead, the insert is performed when
        it shouldn't be.

        The failure occurs because DB2 does not handle an SQLCODE -798
        properly.  This failure can occur for both a local or a
        distributed application.


        The following example illustrates a failing case.

        STEP 1. Create a Table T1 with a GENERATED ALWAYS column.

          CREATE TABLE T1 (ID INT GENERATED ALWAYS AS IDENTITY
                            (START WITH -1,
                                   INCREMENT BY 1,
                                   CYCLE,
                                   MINVALUE -1,
                                   MAXVALUE 100),
                           C2 CHAR(3), C3 VARCHAR(6));


        STEP 2. With an application, perform the following INSERT
                operation.
1
        05  HV1                  PIC S9(4) BINARY.

        05  IND1                 PIC S9(4) BINARY VALUE 0.

          MOVE  1 to HV1.

          EXEC SQL
           INSERT INTO T1 VALUES(:HV1 :IND1, 'FFF', 'TEST1')
          END-EXEC.

        STEP 3. Bind the application using the EXTENDEDINDICATOR bind
                option.

          BIND PACKAGE(PKGSAMP) VALIDATE(RUN) ACTION(REP) -
               MEMBER(PROGA) RELEASE(COMMIT) EXTENDEDINDICATOR(YES)
          BIND PLAN(PLNSAMP) ACTION(REP)   -
               PKLIST(*.PKGSAMP.PROGA) VALIDATE(RUN) -
               RELEASE(COMMIT)


        STEP 4. Execute the package. The insert is performed when it
                should not be.

          RUN  PLAN(PLNSAMP) PROGRAM(PROGA)


        STEP 5. Check the results.

         SELECT * FROM T1;

                     +-------------------------------+
                     |       ID       | C2  |   C3   |
                     +-------------------------------+
                   1_|              1 | FFF | TEST1  |
                     +-------------------------------+

        The insert operation was successful when it should not be.
        Instead, an SQLCODE -798 should be issued.

        The code in DB2 is modified to properly issue and return an
        SQLCODE -151 error to the application when trying to update a
        hash key index column from an application using the
        EXTENDEDINDICATOR bind option.

        Also, when performing an insert to a GENERATED ALWAYS column
        from an application with the EXTENDEDINDICATOR bind option, an
        SQLCODE -798 will be issued and returned to the application.

        Additional Keywords: SQLCODE151 SQLCODE798 SQLUPDATE SQLINSERT
                             SQLINCORR SQLINCORROUT DB2INCORR/K

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM93676
    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
       DSNXRIHB  PM93676
       DSNXRIHD  PM93676
       DSNXRIHR  PM93676
       DSNXRIHS  PM93676

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM93676   DSNXRIHB DSNXRIHD DSNXRIHR DSNXRIHS

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXRIHB
       DSNXRIHD
       DSNXRIHR
       DSNXRIHS

      LISTEND
 UK97296 COVER LETTER END


 UK97305 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM91736 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS, DB2 10 for z/OS, and     *
        *                 DB2 11 for z/OS utility users                *
        ****************************************************************
        * PROBLEM DESCRIPTION: Utility fails in sort with DFSORT       *
        *                      message ICE046A SORT CAPACITY EXCEEDED  *
        *                      followed by ABEND04E RC00E40005 when    *
        *                      sorting short keys with sort work data  *
        *                      sets allocated by DB2 (UTSORTAL=YES).   *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        For some operations the LOAD, REORG TABLESPACE, CHECK INDEX, and
        REBUILD INDEX utilities used sort fields with a precision of
        bits instead of bytes. When the sorted records were very short
        (less than about 25 bytes), then the sort work data sets
        allocated by the utility as indicated by message DSNU3340I
        UTILITY PERFORMS DYNAMIC ALLOCATION OF SORT DISK SPACE may have
        been too small causing MSGICE046A SORT CAPACITY EXCEEDED.

        These sort fields with bit precision can be used when processing
        data partitioned secondary indexes (DPSI), sorting indexed
        foreign keys during LOAD, or when running REORG TABLESPACE
        SHRLEVEL CHANGE.  The bit precision is specified as the
        non-integer part of the field length which is the second
        parameter of a field descriptor as seen in ICE000I message,
        e.g. SORT FIELDS=(00006.0,00000.4,A).

        Additional keywords: MSGDSNU3340I
        Code was changed to allocate additional sort work space for
1       sort fields with bit precision in all affected utilities.

        Code was changed in REORG TABLESPACE SHRLEVEL CHANGE to
        eliminate the use of sort fields with bit precision except when
        the OBID of the mapping table index matches the OBID of any
        other index processed in the same sort task or when
        processing DPSIs.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM91736
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUCRIB  PM91736
       DSNUGALC  PM91736
       DSNUGLSR  PM91736
       DSNUGSOR  PM91736
       DSNUGSRT  PM91736
       DSNUKDXC  PM91736
       DSNUKPIK  PM91736
       DSNURPCT  PM91736
       DSNURPIB  PM91736
       DSNURPSS  PM91736
       DSNURSOR  PM91736
       DSNUSSOR  PM91736

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM91736   DSNUCRIB DSNUGALC DSNUGLSR DSNUGSOR DSNUGSRT DSNUKDXC
                 DSNUKPIK DSNURPCT DSNURPIB DSNURPSS DSNURSOR DSNUSSOR

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUCRIB
       DSNUGALC
       DSNUGLSR
       DSNUGSOR
       DSNUGSRT
       DSNUKDXC
       DSNUKPIK
       DSNURPCT
       DSNURPIB
       DSNURPSS
       DSNURSOR
       DSNUSSOR

      LISTEND
 UK97305 COVER LETTER END


 UK97309 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM94765 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS, DB2 10 for z/OS, and     *
1       *                 DB2 11 for z/OS utility users using          *
        *                 DB2 Sort for z/OS.                           *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C4 RC0000003B in DSNUGSOR         *
        *                      +X'2004' when sorting with DB2 Sort     *
        *                      for z/OS.                               *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        Some portions of the E15 and E35 sorting exits operate in 64 bit
        addressing mode. In the failing case the E35 exit was invoked
        with a non zero value in the upper half of a register that was
        used as a base register in the exit. This pointed to an invalid
        address when executing in 64 bit mode which resulted in the
        ABENDS0C4 at DSNUGSOR OFFSET2004.
        Code has been changed to clear the upper word of the used basing
        registers on entry to the sort exits.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM94765
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUGLSR  PM94765
       DSNUGSOR  PM94765
       DSNUKXSR  PM94765

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM94765   DSNUGLSR DSNUGSOR DSNUKXSR

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUGLSR
       DSNUGSOR
       DSNUKXSR

      LISTEND
 UK97309 COVER LETTER END


 UK97332 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86847 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS users of DB2 command        *
        *                 -ACCESS DATABASE SPACENAM MODE(OPEN)         *
        ****************************************************************
        * PROBLEM DESCRIPTION: DB2 V10 command -ACCESS DATABASE        *
        *                      SPACENAM MODE(OPEN) may fail with       *
        *                      msgDSNI045I OPEN FAILED REASON 0000001E *
        *                      on DEFINE NO objects.  For V9, the      *
        *                      REASON is 00000000.                     *
        ****************************************************************
        * RECOMMENDATION:                                              *
1       ****************************************************************
        -ACCESS DB command with MODE(OPEN) may fail with REASON 0000001E
        or 00000000 on a DEFINE NO object if the data set has not been
        defined yet.
        Instead of issuing OPEN FAILED with reason 0000001E or 00000000,
        the code is changed to skip processing DEFINE NO tablespace or
        index if the associated data set has not been created yet.

        DB2 Command Reference will be updated to add the following under
        -ACCESS DATABASE MODE(OPEN) section:

        When MODE(OPEN) is specified, DB2 does not process objects with
        both of the following characteristics:
        - The objects are defined with DEFINE NO.
        - The physical data sets for the objects have not been created.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM86847
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNTDMST  PM86847

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM86847   DSNTDMST

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNTDMST

      LISTEND
 UK97332 COVER LETTER END


 UK97360 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM92272 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 and 11 for z/OS users of a        *
        *                 static SQL statement that has a non-boolean  *
        *                 term BETWEEN predicate with a Timestamp      *
        *                 column and host variables.                   *
        ****************************************************************
        * PROBLEM DESCRIPTION: Performance regression could happen for *
        *                      a static SQL statement that has a       *
        *                      non-boolean term BETWEEN predicate with *
        *                      a Timestamp column and host variables.  *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Performance regression could happen for a static SQL statement
        that has a non-boolean term BETWEEN predicate with a Timestamp
        column and host variables.

1       An examples is shown below:

        CREATE TABLE T1 (C1 CHAR(16), C2 TIMESTAMP);

        CREATE INDEX IX1 ON T1 (C1);
        CREATE INDEX IX2 ON T1 (C2);

        SELECT C1
        INTO :HV1
        FROM T1
        WHERE (:HV2 > 0 AND C1 = 'X')
              OR C2 BETWEEN :HV3 AND :HV4;

        Multiple-index access can not be well used for the above static
        SQL statement, while it could on DB2 9 for z/OS.

        DB2 did not correctly process the aforementioned SQL statements,
        which caused the performance regression.
        DB2 has been modified to correctly process the aforementioned
        SQL statement, so there will be no the performance regression as
        multiple-index access can be well used.

        Additional keywords: SQLTIMESTAMP SQLHOSTVAR SQLACCESSPATH,
                             SQLPERFORMANCE MIDX MULTIINDEX SQLBETWEEN
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM92272
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM92272:

        See PM92272 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM92272 corrects a problem that performance regression could
        happen for a static SQL statement that has a non-boolean term
        BETWEEN predicate with a Timestamp column and host variables.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOW2C  PM92272
       DSNXOW2D  PM92272

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM92272   DSNXOW2C DSNXOW2D

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOW2C
       DSNXOW2D
1
      LISTEND
 UK97360 COVER LETTER END


 UK97362 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM92200 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS users with segmented        *
        *                 table spaces (non-UTS) that applied          *
        *                 APAR PM75921 (PTF UK91122).                  *
        ****************************************************************
        * PROBLEM DESCRIPTION: Cluster order may be compromised for    *
        *                      segmented table spaces (non-UTS) after  *
        *                      applying APAR PM75921 (PTF UK91122).    *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available.         *
        ****************************************************************
        After applying APAR PM75921 (PTF UK91122), clustering order for
        segmented table space (non-UTS) may become compromised, which
        may lead to deadlocks and timeouts, RC00C90088 and RC00C9008E.

        While inserting data, the clustering index failed to provide a
        viable candidate page. Based upon very data dependant factors,
        a candidate page was returned that was not useable since it was
        already full. This caused data to be appended to the end of the
        table space, compromising clustering order.
        DB2 has been modified so that when the clustering index for a
        segmented table space (non-UTS) is used to determine the
        candidate page for insert, it will provide a more viable
        candidate page.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM92200
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNKPOSI  PM92200

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM92200   DSNKPOSI

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNKPOSI

      LISTEND
 UK97362 COVER LETTER END


 UK97369 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89459 -
1       ****************************************************************
        * USERS AFFECTED: All DB2 10 and 11 for z/OS users             *
        *                 of parallelism.                              *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00E2000C at location         *
        *                      DSNXPCRT DSNSVSVB +0B10 can occur when  *
        *                      using parallelism.                      *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        ABEND04E RC00E2000C at location DSNXPCRT.DSNSVSVB+0B10
        can occur when using parallelism.

        Storage allocated for parallelism internal structures are
        not completely freed under certain circumstances, when DB2
        goes through an error path. Accumulated storage leaked will
        cause storage abend observed in this problem.

        The problem is not query specific, and it could happen when
        a query is running in parallel. The query abend could be a
        victim of storage leak by previous queries.

        DB2 has been fixed to free parallel storage completely
        for a query running under parallel plan. The storage
        leak no longer occurs for this circumstance.

        Additional keywords: DB2PARALL/K  PARALLELISM SQLPARALLELISM
                             DB2STGLK/K    SQLSTORAGE
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89459
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXPDAL  PM89459
       DSNXPDST  PM89459
       DSNXRTSS  PM89459

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89459   DSNXPDAL DSNXPDST DSNXRTSS

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXPDAL
       DSNXPDST
       DSNXRTSS

      LISTEND
 UK97369 COVER LETTER END


 UK97375 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM93390 -
1       ****************************************************************
        * USERS AFFECTED: All DB2 11, DB2 10 and DB2 9 for z/OS users  *
        *                 of REORG utility in data sharing when        *
        *                 running concurrently with -DISPLAY DATABASE  *
        *                 CLAIMERS/LOCKS command.                      *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C4 DSNICMT2+778E and ABEND04E     *
        *                      RC00C90101 DSNIFPSC ERQUAL5001 while    *
        *                      REORG SHRLEVEL CHANGE utility was       *
        *                      running concurrently with -DISPLAY      *
        *                      DATABASE CLAIMERS/LOCKS command,        *
        *                      potentially followed by DB2 crash.      *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When running REORG utility to convert a classic-partitioned
        table space to universal table space (UTS), the REORG utility
        during its SWITCH phase updated the DBD to show the new table
        space attributes. A -DISPLAY DATABASE CLAIMERS notify exit was
        being processed while the REORG was running.

        Before the REORG physically closed the table space, attributes
        for the object were mismatched between the DBD and the internal
        PB structure, which led to the abend ABEND0C4 in DSNICMT2 on
        the command's notify exit task (the DBD it was looking at was
        still downlevel).

        The -DISPLAY DATABASE command needs to acquire a DBD lock to
        make sure that the DBD is refreshed before the command accesses
        it.
        DB2 code has been modified to acquire a DBD lock during the
        -DISPLAY DATABASE command to make sure the DBD is refreshed.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM93390
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNIBCTD  PM93390

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM93390   DSNIBCTD

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIBCTD

      LISTEND
 UK97375 COVER LETTER END


 UK97384 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM94885 -
1       ****************************************************************
        * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
        *                 Specifically where DB2 is being accessed     *
        *                 by distributed applications using the IBM    *
        *                 Data Server Driver or Client product family  *
        *                 and the packages utilized by the application *
        *                 were bound with KEEPDYNAMIC(YES).            *
        ****************************************************************
        * PROBLEM DESCRIPTION: Message pair DSNL027I/DSNL028I, with    *
        *                      reason codes 00D3003E and 00D3003F,     *
        *                      is issued periodically after APAR       *
        *                      PM43293.                                *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        One of the stated goals of APAR PM43293 was to provide
        additional serviceability information during various
        DDF thread termination events.  Prior to the APAR, a thread
        could be terminated by DDF without sufficient diagnostic
        information if the thread had been used by a distributed
        client connection under KeepDynamic Refresh rules (see APAR
        PK69339).  APAR PM43293 implemented the periodic displaying
        of messages DSNL027I/DSNL028I if a thread/connection had been
        terminated under KeepDynamic Refresh rules due to being used
        for too long (1 hour) or idle for too long (20 minutes), but
        these messages could cause unnecessary alarm for essentially
        normal operational events.

        DB2 has been changed to no longer issue the DSNL027I/DSNL028I
        message pair due to KeepDynamic Refresh events.  In its
        place, DB2 will now record the events in LOGREC with 00D3003E
        and 00D3003F reason codes.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM94885
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNLBABR  PM94885
       DSNWDSDM  PM94885
       DSNWSDWA  PM94885

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM94885   DSNLBABR DSNWDSDM DSNWSDWA

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNLBABR
       DSNWDSDM
       DSNWSDWA

      LISTEND
 UK97384 COVER LETTER END

1
 UK97386 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM93511 -
        ****************************************************************
        * USERS AFFECTED: DB2 data sharing users.                      *
        ****************************************************************
        * PROBLEM DESCRIPTION: Storage leak in a BB1RMID storage pool, *
        *                      with a large number of small page list  *
        *                      blocks allocated by DSNB1ULT.           *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        If a castout request is issued for a pageset, and the GBP is
        defined as GBPCACHE=NO, the castout engine will exit without
        doing any work because there's nothing in the GBP to cast out.
        However, if a page list was provided with the castout request
        (which may happen during an image copy), the engine neglects
        to free the page list storage on the way out, so over time the
        storage for these lists can accumulate.
        The castout logic has been modified to free the storage for any
        page lists when taking an early exit due to the GBP being set to
        GBPCACHE=NO.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM93511
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNB5PCO  PM93511

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM93511   DSNB5PCO

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNB5PCO

      LISTEND
 UK97386 COVER LETTER END


 UK97390 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM91349 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of       *
        *                 EXISTS subqueries.                           *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E at DSNXGRDS DSNXOEXB M200      *
        *                      may occur for and SQL statement that    *
        *                      contains an EXISTS subquery and the     *
        *                      EXISTS subquery contains a correlated   *
        *                      subquery in the SELECT list.            *
1       ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        ABEND04E at DSNXGRDS DSNXOEXB M200 may occur for an SQL
        statement that contains an EXISTS subquery and the
        EXISTS subquery contains a correlated subquery in the
        SELECT list.

        For Example,

        SELECT DISTINCT C1 FROM T1
           WHERE EXISTS
                (SELECT CASE
                   WHEN T3.C1 = 'A' THEN
                     (SELECT 'A' FROM T2 WHERE T2.C1 = T3.C1)
                   ELSE 'B' END
                 FROM T3
                 WHERE T3.C1 = T1.C1
                    )
           AND T1.C1 = 'B';

        The statement above may cause an abend because DB2 did not
        process the correlated subquery in the SELECT list correctly.
        After this apar fix, DB2 will disable the EXISTS subquery
        transformation if there is a correlated subquery in the
        SELECT list.

        Additional Keywords: SQLEXISTS SQLJOIN SQLSUBQUERY SQLCORRSUBQ
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM91349
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      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.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOQJ1  PM91349

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM91349   DSNXOQJ1

1     THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOQJ1

      LISTEND
 UK97390 COVER LETTER END


 UK97396 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM93896 -
        ****************************************************************
        * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
        *                 Especially those that utilize TCP/IP         *
        *                 communications to access remote locations    *
        *                 from DB2 for z/OS requesters or use          *
        *                 trusted connection processing with           *
        *                 inbound client connections.                  *
        ****************************************************************
        * PROBLEM DESCRIPTION: Possible symptoms may include:          *
        *                      - ABEND 04E-00E20013                    *
        *                        at DSNSLD1.DSNSGMN+05CA               *
        *                      - ABEND 04E-00E20003                    *
        *                        at DSNLXPAL.DSNSVBK+0606              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        A DB2 for z/OS DDF requester will always need to request
        name resolution services from TCP/IP if the IPADDR column in
        an SYSIBM.IPNAMES row is a domain name, as opposed to an
        IPv4 or IPv6 address.
        A DB2 for z/OS DDF server will always need to request name
        resolution services from TCP/IP if a domain name is provided
        in the context definition of a trusted inbound client
        connection.
        The name resolution service involves two calls to TCP/IP.  The
        first call causes TCP/IP to acquire storage in the DB2 ssnmDIST
        address space that contains the required information.  Once
        the information is processed by DB2, the second call causes
        TCP/IP to free the storage that it acquired.
        DB2 corrupted the storage address provided to TCP/IP during
        the second call.  As a result, the storage is not freed which
        causes a storage leak leading to various Short On Storage
        related symptoms.

        DB2 has been changed to ensure the storage address it obtains
        via any TCP/IP name resolution service request is subsequently
        passed back to TCP/IP during the free name resolution service
        resources requests.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM93896
    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
       DSNLIDNS  PM93896
       DSNLILE   PM93896
       DSNLILNR  PM93896
       DSNLIRQP  PM93896

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM93896   DSNLIDNS DSNLILE  DSNLILNR DSNLIRQP

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNLIDNS
       DSNLILE
       DSNLILNR
       DSNLIRQP

      LISTEND
 UK97396 COVER LETTER END


 UK97423 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM94348 -
        ****************************************************************
        * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
        *                 Specifically where DB2 for z/OS is utilized  *
        *                 as a requester to connect to a DB2 for VSE   *
        *                 & VM server.                                 *
        *                 DB2 10/11 for z/OS users only.               *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND=0C4-00000004                      *
        *                      LOC=DSNLZGLM.DSNLZRDA+0E68              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        DB2 10/11 for z/OS requester processing is accessing invalid
        storage when connecting to a remote DB2 for VSE & VM server,
        which results in the reported abend symptom.

        DSNLZRDA has been changed to validate the presence of the
        storage being accessed.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM94348
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNLZRDA  PM94348

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM94348   DSNLZRDA

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

1     MODULES
       DSNLZRDA

      LISTEND
 UK97423 COVER LETTER END


 UK97427 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM91469 -
        ****************************************************************
        * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
        *                 Specifically where DB2 for z/OS is utilized  *
        *                 as a requestor and TIMESTAMP WITH TIME ZONE  *
        *                 data type (SQLTYPE 2448/2449) is used.       *
        *                 DB2 10/11 for z/OS users only.               *
        ****************************************************************
        * PROBLEM DESCRIPTION: The statement fails with SQLCODE180     *
        *                      (-180).                                 *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When an application executes a remote SQL statement with
        TIMESTAMP WITH TIME ZONE input data (SQLTYPE 2448/2449), the
        DB2 for z/OS requestor incorrectly truncates 2 bytes from the
        data before sending it to the server.  The server correctly
        detects the invalid date and fails the statement.

        DSNLZRDT has been changed to use the correct data length for the
        TIMESTAMP WITH TIME ZONE data type (SQLTYPE 2448/2449).
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM91469
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNLZRDT  PM91469

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM91469   DSNLZRDT

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNLZRDT

      LISTEND
 UK97427 COVER LETTER END


 UK97465 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM95277 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of SQL             *
1       *                 table functions.                             *
        ****************************************************************
        * PROBLEM DESCRIPTION: AE PM89329 FIX COMPLETION               *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        AE PM89329 FIX COMPLETION
        AE PM89329 FIX COMPLETION

        Additional Keywords:  SQLINLINE SQLTABLEUDF
                              SQLINCORR INCORROUT SQLINCORROUT
                              DB2INCORR/K SQLCODE180 SQLUDF

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM95277
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for  PM95277

        See  PM95277 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM95277 corrects an incorrect output problem that can occur for
        an SQL statement that references an SQL table function.

        The incorrect output can occur for the following cases:

        1. The SQL statement references an SQL table function and a
        view.
        2. The SQL statement references a multi-level nested
        SQL table function  and the argument of the SQL table function
        contains a column expression.
        3. The SQL statement references an SQL table function in the
        subquery predicate and the SQL table function is materialized.

        To make this fix effective for a static application, it must 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  PM89329

        See  PM89329APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM89329 corrects a problem of incorrect out put may occur for an
        SQL statement that references an SQL table function. Incorrect
        out put may occur for the following cases:
        1. The SQL statement references an SQL table function and a
        view .
        2. The SQL statement references a multi-level nested
        SQL table function  and the argument of the SQL table function
        contains a column expression.
        3. The SQL statement references an SQL table function in the
1       subquery predicate and the SQL table function is materialized.

        To make this fix effective for a static application, it must 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
       DSNXOCF   PM95277

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM95277   DSNXOCF

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOB1
       DSNXOCF
       DSNXOEXC
       DSNXOJAJ
       DSNXOOS2
       DSNXOVC
       DSNXOVM

      LISTEND
 UK97465 COVER LETTER END


 UK97468 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM95020 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of      *
        *                 Workfile database (e.g. sort workfiles,      *
        *                 declared global temporary tables (DGTT),     *
        *                 etc.) when the zparm WFDBSEP is YES          *
        ****************************************************************
        * PROBLEM DESCRIPTION: When zparm WFDBSEP is YES (indicating   *
        *                      hard separation between Workfile table  *
        *                      spaces for sort workfile vs. DGTT       *
        *                      activity), if the sort workfile table   *
        *                      spaces are full, sort workfile work     *
        *                      may still spill into DGTT table spaces  *
        *                      by mistake, despite the zparm being on  *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When zparm WFDBSEP is YES, workfile table space usage is
        expected to be unconditionally split between sort workfile work
        and DGTT work, based on the physical attributes of the table
        spaces.

        However, during sort workfile activity, when the sort workfile-
        designed table spaces were full, spilling into a DGTT-designed
        table space with 4K page size was still observed. The code was
        mistakenly not honoring the zparm in this 4K code path.
1       Code has been changed to ensure that the zparm WFDBSEP YES is
        honored (and resource-not-available issued) when no more space
        is available in the sort workfile-designation category.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM95020
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNIGWAC  PM95020

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM95020   DSNIGWAC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIGWAC

      LISTEND
 UK97468 COVER LETTER END


 UK97483 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM94968 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of       *
        *                 hybrid join with ROWID data.                 *
        ****************************************************************
        * PROBLEM DESCRIPTION: An ABEND04E RC00C900D0 at location      *
        *                      DSNXROHB 1CD6E (OFFSET1CD6E) can occur  *
        *                      when a query references ROWID data      *
        *                      followed by LOB data when using a       *
        *                      hybrid join access path.                *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An ABEND04E RC00C900D0 can occur at location DSNXROHB 1CD6E
        (OFFSET1CD6E) when a query references ROWID data that is
        followed by LOB data when using a hybrid join access path.

        The following example helps to illustrate the problem.

        Step 1. Create two tables, each with a unique index.

          CREATE TABLE T1 (C1 INT,  C2 ROWID NOT NULL, C3 CLOB(100));
          CREATE TABLE T2 (C1 INT,  C2 ROWID NOT NULL, C3 CLOB(100));

          CREATE UNIQUE INDEX IX1 ON T1(C1);
          CREATE UNIQUE INDEX IX2 ON T2(C1) CLUSTER;


        Step 2. Insert three rows of data into each table.

1         INSERT INTO T1 VALUES(1,DEFAULT,CLOB('ABC'));
          INSERT INTO T1 VALUES(2,DEFAULT,CLOB('ABC'));
          INSERT INTO T1 VALUES(3,DEFAULT,CLOB('ABC'));

          INSERT INTO T2 VALUES(1,DEFAULT,CLOB('AB2'));
          INSERT INTO T2 VALUES(2,DEFAULT,CLOB('AB2'));
          INSERT INTO T2 VALUES(3,DEFAULT,CLOB('AB2'));


        Step 3. Perform the following select statement using a hybrid
                join access path.

          SELECT  A.C1, HEX(A.C2), B.C2, A.C3
          FROM T1 A, T2 B
          WHERE A.C1 = B.C1 ;


        The ROWID column B.C2 is not moved correctly by DB2 and as a
        result, it eventually overlays the storage for the next column,
        CLOB column A.C3.  This leads to the above mentioned abend.

        Please note:  If A.C3 is replaced by another data type, an
        incorrect result for both B.C2 and the other data type or an
        unexpected abend in another DB2 module can occur due to a memory
        overlay.
        The code in DB2 has been modified to correctly move the ROWID
        data using the actual length instead of the declared length.
        This will prevent the above abend and the incorrect output.

        Additional Keywords: SQLHYBRIDJOIN SQLROWID SQLINCORR INCORROUT
                             SQLINCORROUT DB2INCORR/K DB2OVRLAY/K
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM94968
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXRFHJ  PM94968
       DSNXRGBJ  PM94968
       DSNXRSFJ  PM94968

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM94968   DSNXRFHJ DSNXRGBJ DSNXRSFJ

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXRFHJ
       DSNXRGBJ
       DSNXRSFJ

      LISTEND
 UK97483 COVER LETTER END


1UK97488 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM93267 -
        ****************************************************************
        * USERS AFFECTED: DB2 10 and DB2 9 for z/OS users of sequence  *
        *                 objects (IDENTITY column, stand-alone        *
        *                 SEQUENCE)                                    *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNIFSQD ERQUAL5006 *
        *                      during operation that involves          *
        *                      sequences, running concurrently with    *
        *                      closure of table space DSNDB06.SYSSEQ   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        While accessing an internal sequence descriptor control block in
        memory for a single sequence object, the code issued an abend
        when it detected an inconsistency in the control block, without
        knowing that the inconsistency was due to a concurrent 'close'
        process for the DSNDB06.SYSSEQ table space and that the
        inconsistency was actually acceptable, simply requiring that the
        code take an alternate path, increasing the chance of the SQL
        succeeding.
        Code has been modified to not issue the abend when it is not
        warranted and instead drive an alternate code path and try to
        have the SQL succeed.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM93267
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNIFSQD  PM93267
       DSNIQISE  PM93267

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM93267   DSNIFSQD DSNIQISE

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIFSQD
       DSNIQISE

      LISTEND
 UK97488 COVER LETTER END


 UK97517 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM93269 -
        ****************************************************************
        * USERS AFFECTED: ALL DB2 9, DB2 10, and DB2 11 for z/OS       *
        *                 users.                                       *
        ****************************************************************
1       * PROBLEM DESCRIPTION: There are several problems solved.      *
        *                                                              *
        *                      1.  ABEND0C4 RC=04 in DSNXOWPT +0902    *
        *                      2.  ABEND0C4 RC=04 in DSNXQMCH +069C    *
        *                      3.  SQLCODE -583 on a SELECT from view. *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        There are several problems solved.


        Problem 1 occurs on a SELECT from a table with row permissions
        and other possible SELECT statements.
        Problem 2 occurs on a SELECT from an XMLTABLE with an XML
        index defined.
        Problem 3 occurs on a SELECT from a view on DB2 11 for z/OS.
        DB2 has been fixed to handle the problems described.

        Additional Keywords:  SQLSELECT SQLVIEW SQLCODE583 SQLXML
                              OFFSET0902 OFFSET069C
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM93269
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOVC   PM93269
       DSNXOWPT  PM93269
       DSNXQMCH  PM93269

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM93269   DSNXOVC  DSNXOWPT DSNXQMCH

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOVC
       DSNXOWPT
       DSNXQMCH

      LISTEND
 UK97517 COVER LETTER END


 UK97524 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89636 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS users of created global     *
        *                 temporary tables (CGTT)                      *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNIWTTD ERQUAL500A *
        *                      may occur during close of cursor on     *
        *                      CGTT if the CGTT has previously been    *
        *                      internally stored by DB2 on more than   *
1       *                      one physical workfile table space       *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        A created global temporary table (CGTT) had several cursors on
        it and during insert into the CGTT DB2 had to expand this CGTT
        to more than one physical workfile table space.

        During an internal restore to savepoint, the CGTT was restored
        back to its original table space alone, however a pointer in the
        internal reader CUB structure was not reset and still pointed to
        an extension reader CUB that represented one of the table spaces
        that the CGTT was expanded to (even though this secondary
        workfile table space was no longer in the picture).

        As a result, during cursor close (reader CUB deletion), DB2
        abended because said pointer was pointing to the freed extension
        reader CUB.
        Code has been changed to reset pointers to internal extension
        reader CUBs during internal restore to savepoint.

        Additional keywords: SQLCGTT
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89636
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNIWTTD  PM89636

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89636   DSNIWTTD

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIWTTD

      LISTEND
 UK97524 COVER LETTER END


 UK97538 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM95153 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS customers using             *
        *                 UPDATE through a symmetric view.             *
        ****************************************************************
        * PROBLEM DESCRIPTION: SQLCODE161 is issued when               *
        *                      updating a table through a              *
        *                      symmetric view, even though the         *
        *                      new value satisfies the view            *
        *                      definition.                             *
        ****************************************************************
1       * RECOMMENDATION:                                              *
        ****************************************************************
        Sqlcode SQLCODE161 is issued from an UPDATE statement
        when the view definition contains include columns AND
        the include columns are part of the view definition.

        An index was used to verify whether a newly updated value
        satisfies a view definition.  The index contained include
        columns in the key, and the include columns were part of
        the view definition.

        DB2 incorrectly disallowed the UPDATE.

        Additional keywords:
        SQLVIEW
        DB2 has been modified to correctly evaluate the view definition
        predicates when include columns are involved.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM95153
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNISTRI  PM95153

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM95153   DSNISTRI

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNISTRI

      LISTEND
 UK97538 COVER LETTER END


 UK97542 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM92588 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9, DB2 10 and DB2 11                 *
        *                 for z/OS users of decimal datatype           *
        *                 and transitive closure.                      *
        ****************************************************************
        * PROBLEM DESCRIPTION: An ABEND0C7 RC00000000 occurred at      *
        *                      DSNXRINT OFFSET 3EF2 for an SQL         *
        *                      statement that satisfies all of         *
        *                      the following conditions:               *
        *                      1. The statement contains an DB2        *
        *                      generated equal, IN or BETWEEN          *
        *                      transitive closure predicate.           *
        *                      2. The generated transitive closure     *
        *                      predicate references a column and       *
        *                      a host variable.                        *
1       *                      3. The column was a not null decimal    *
        *                      and a NULL value was sent in during     *
        *                      execution time for the host variable.   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        For Example,

        CREATE TABLE T1 (C1 INT, C2 DECIMAL NOT NULL);
        INSERT INTO T1 VALUES (1,1.2);
        SELECT C1 FROM T1 WHERE C1 = C2 AND C2 = :HV1;

        DB2 generated transitive closure predicate:
          C1 = :HV1

        When a NULL value is sent in for :HV1, the above SELECT
        statement results in an ABEND0C7 failure.

        DB2 was modified to handle the NULL value correctly for the
        transitive closure predicate described in the example.

        Additional keywords: SQLNULL SQLTRANSCLOSURE SQLPREDICATE
                             SQLHOSTVAR SQLPARAMETERMARKER
                             OFFSET3EF2 SQLNOTNULL
                             SQLEQUAL SQLIN SQLBETWEEN





    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM92588
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM92588:

        See PM92588 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM92588 corrects a problem of ABEND0C7 at DSNXRINT OFFSET 3EF2
        for an SQL statement that satisfies all of the following
        conditions:
        1. The statement contains an DB2 generated equal, IN or
        BETWEEN transitive closure predicate.
        2. The generated transitive closure predicate references a
        column and a host variable.
        3. The column was a not null decimal and a NULL value was
        sent in during execution time for the 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.
      DB2BIND:
1       ***Action for PM83563:

        See PM83563 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM83563 corrects a problem that matching index access is
        incorrectly used for an SQL statement that contains a predicate
        with a 'Non-column expression CONCAT empty string' when the
        column comparing to this expression is Timestamp 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.
      DB2BIND:
        ***Action for PM79953:

        See PM79953 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM79953 corrects a problem of an inefficient access path being
        chosen by DB2 for a SQL statement which satisfies the following
        conditions:
        1.it contains a VALUE COMPARE predicate or a BETWEEN predicate
          with an arithmetic expression,
        2.the arithmetic expression has a host variable or parameter
          marker and integer constant as its operators,
        3.matching index access is possible for the query.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM76452:

        See PM76452 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM76452 corrects a problem of ABEND0C7 RC0 at DSNXRDEC +59BC
        when a transitive closure predicate takes the form of column =
        host variable where the column is a not null decimal and a
        NULL value was sent in during execution time for the host
        variable.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOMEX  PM92588
       DSNXOW2F  PM92588

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM92588   DSNXOMEX DSNXOW2F
1
      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOMEX
       DSNXOW2F

      LISTEND
 UK97542 COVER LETTER END


 UK97556 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM88702 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS, DB2 10 for z/OS and      *
        *                 DB2 11 for z/OS users of RECOVER utility     *
        *                 and COPY utility with FLASHCOPY CONSISTENT.  *
        ****************************************************************
        * PROBLEM DESCRIPTION: RECOVER utility and COPY utility with   *
        *                      FLASHCOPY CONSISTENT specified do not   *
        *                      respond to the -TERM UTIL command.      *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available.         *
        ****************************************************************
        The RECOVER utility and COPY utility with FLASHCOPY CONSISTENT
        specified do not respond to the -TERM UTIL command during
        the LOGAPPLY and LOGUNDO phases due to incorrect handling of
        return codes.
        The RECOVER utility and COPY utility code has been modified
        to correctly detect a -TERM UTIL command during the LOGAPPLY
        and LOGUNDO phases.  Note that in the case of RECOVER utility
        the affected object(s) will be left in RECOVER PENDING (RECP)
        status and in both cases the utility will terminate with RC8,
        which is expected when the utility has been terminated with the
        -TERM UTIL command.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM88702
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNIFLRD  PM88702
       DSNIREDO  PM88702
       DSNUBBFC  PM88702
       DSNUCACL  PM88702
       DSNUCALA  PM88702
       DSNUCALU  PM88702
       DSNUCALZ  PM88702

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM88702   DSNIFLRD DSNIREDO DSNUBBFC DSNUCACL DSNUCALA DSNUCALU
                 DSNUCALZ

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1
      MODULES
       DSNIFLRD
       DSNIREDO
       DSNUBBFC
       DSNUCACL
       DSNUCALA
       DSNUCALU
       DSNUCALZ

      LISTEND
 UK97556 COVER LETTER END


 UK97573 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM96572 -
        ****************************************************************
        * USERS AFFECTED: All Users of DB2.                            *
        ****************************************************************
        * PROBLEM DESCRIPTION: DB2 ABEND DURING RESTART RC00C90101     *
        *                      DSNIECUR ERQUAL5004.                    *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When Unit of Recovery (UR) Summary Checkpoint log record
        includes declared global temporary table (DGTT), although they
        are defined as Universal Table Space (UTS), but when it is
        logged in UR summary checkpoint log record, DGTT is logged as
        segmented. Which means that it logs table OBID instead of
        partition number, which is typically done for non-DGTT UTS
        objects. This results in false sanity check when processing DGTT
        information in UR summary checkpoint log record during restart.
        The restart log processing logic is adjusted so that it will
        correctly differentiate when the log record includes partition
        number and when it includes table OBID for UTS object.
        DB2 restart logic is corrected to avoid false detection of
        invalid partition number which prevents successful DB2 restart.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM96572
    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  PM96572

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM96572   DSNIECUR

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIECUR

      LISTEND
1UK97573 COVER LETTER END


 UK97593 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM94190 -
        ****************************************************************
        * USERS AFFECTED: Users of DB2 for z/OS star join              *
        *                 with BIGINT data types.                      *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND 04E-00E70005,LOC=                 *
        *                      DSNXGRDS.DSNXOPKY:M030 may occur        *
        *                      when the following conditions are       *
        *                      met:                                    *
        *                      1. The query qualifies as a star        *
        *                      schema;                                 *
        *                      2. An index on the fact table has       *
        *                      one or more index keys with the         *
        *                      BIGINT/BINARY/VARBIN data type; and     *
        *                      3. A pushdown plan is chosen with       *
        *                      JOIN_TYPE='S' in the PLAN_TABLE.        *
        *                                                              *
        *                      SQLSTARJOIN ABEND04E RC00E70005         *
        *                      SQLPAIRWISEJOIN                         *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        ABEND 04E-00E70005,LOC=DSNXGRDS.DSNXOPKY:M030 may occur
        when the following conditions are met:

        1. The query qualifies as a star schema;
        2. An index on the fact table has one or more keys with the
           BIGINT/BINARY/VARBIN data type; and
        3. A pushdown plan is chosen with JOIN_TYPE='S' in the
           PLAN_TABLE.

        The abend occurs because DB2 does not support BIGINT / BINARY /
        VARBIN data types for a star join pushdown plan.
        The problem described above is fixed by not using
        the fact table index with unsupported data types of
        BIGINT / BINARY / VARBIN in a star join pushdown or
        pair-wise join plan.

        The fix may cause an access path change for queries
        that are eligible for a star join pair-wise join plan.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM94190
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOSJD  PM94190
       DSNXOSJX  PM94190

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
1      PM94190   DSNXOSJD DSNXOSJX

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOSJD
       DSNXOSJX

      LISTEND
 UK97593 COVER LETTER END


 UK97603 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM91547 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10, DB2 9 and DB2 V8 for z/OS data   *
        *                 sharing users of the z/OS SETXCF REBUILD     *
        *                 command when issued against SCA              *
        ****************************************************************
        * PROBLEM DESCRIPTION: Timeout MSGDSNT376I MSGDSNT501I with    *
        *                      RC00C900C0 TYPE00002105 may occur in    *
        *                      data sharing when a REBUILD of the SCA  *
        *                      structure is issued (e.g.               *
        *                      SETXCF START,REBUILD,STRNM=DSNCAT_SCA), *
        *                      resulting in stoppage of the rebuild,   *
        *                      with messages MSGDSN7504I, MSGIXC522I   *
        *                      and MSGIXC521I, caused by concurrent    *
        *                      mainline DBET updater that happens to   *
        *                      be in the notify exit path              *
        *                                                              *
        *                      Please note:                            *
        *                      PM91547 is the enabling APAR for a      *
        *                      portion of APAR PM69760's code. This    *
        *                      enablement was originally shipped in    *
        *                      APAR PM74803 however, coincidentally    *
        *                      the functionally unrelated PE-fixer     *
        *                      APAR PM77066 happened to be based on    *
        *                      the aforementioned preconditioning and  *
        *                      enabling APARs. APAR PM91546 has been   *
        *                      provided in order to spare users from   *
        *                      the burden of applying the              *
        *                      preconditioning APAR PM69760 on all     *
        *                      members of a data sharing group just to *
        *                      get to apply the PE-fixer APAR PM77066. *
        *                      APAR PM91546 temporarily removed the    *
        *                      enabling support that was originally    *
        *                      in APAR PM74803. PM91547 now restores   *
        *                      the enablement.                         *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        REBUILD of the SCA structure may experience a timeout on
        resource type 00002105 when running concurrently with
        database exception table (DBET)-heavy activity such as
        utility workloads that turn on/off various DBET states like
1       UTRW, RBDP etc.

        The following sample illustrates the issue:
        ----------------------------------------------------------------
        DSNT376I  - PLAN=BCT      WITH 398
                CORRELATION-ID=014.RBDBET01
                CONNECTION-ID=V91A
                LUW-ID=DSNCAT.SYEC1DB2.CA3071BF1397
                THREAD-INFO=SYSOPR:*:*:*
                IS TIMED OUT. ONE HOLDER OF THE RESOURCE IS PLAN=
        WITH
                CORRELATION-ID=020.JOBSTO07
                CONNECTION-ID=V91A
                LUW-ID=DSNCAT.SYEC1DB2.CA3071B10954=7
                THREAD-INFO=SYSOPR:*:*:*
                ON MEMBER V91A

        DSNT501I  - DSNILMCL RESOURCE UNAVAILABLE 399
                   CORRELATION-ID=014.RBDBET01
                   CONNECTION-ID=V91A
                   LUW-ID=DSNCAT.SYEC1DB2.CA3071BF1397=0
                   REASON 00C900C0
                   TYPE 00002105
                   NAME INTERNAL LOCK 05

        DSN7504I  - DSN7LST2 400
        SCA STRUCTURE DSNCAT_SCA REBUILD UNSUCCESSFUL. REASON CODE =  8.

        IXC522I REBUILD FOR STRUCTURE 401
        DSNCAT_SCA IS BEING STOPPED
        TO FALL BACK TO THE OLD STRUCTURE DUE TO
        CONNECTOR SPECIFIC REASON
         USER CODE: 00000008

        IXC521I REBUILD FOR STRUCTURE DSNCAT_SCA 405
        HAS BEEN STOPPED
        ----------------------------------------------------------------

        The reason for the timeout of the SCA REBUILD is that a mainline
        DBET updater (e.g. a utility) is suspended (while holding the
        DBET hash lock) by the SCA REBUILD process. When the SCA REBUILD
        tries to obtain the same lock, it cannot do so because the
        holder is suspended and therefore the SCA REBUILD times out.

        APAR PM91547 is particularly for the timing window when the SCA
        REBUILD tries to obtain the DBET hash lock while a mainline DBET
        updater is in the notify exit path.
        Code has been changed to adjust the serialization scheme
        between mainline DBET updaters and the SCA REBUILD process.

        APAR PM91547 is the enabling APAR for a portion of APAR PM69760.
        APAR PM91547 should be applied only after APAR PM69760 has been
        applied on all data sharing members.

        Additional keywords: DB2DSHR SYSPLEXDS
    COMPONENT:  5740-XYR00-HDBAA10
1   APARS FIXED: PM91547
    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.
        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
       DSNIDBEL  PM91547
       DSNIDBGN  PM91547
       DSNIDBGR  PM91547
       DSNIDBNG  PM91547

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM91547   DSNIDBEL DSNIDBGN DSNIDBGR DSNIDBNG

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIDBEL
       DSNIDBGN
       DSNIDBGR
       DSNIDBNG

      LISTEND
 UK97603 COVER LETTER END


 UK97630 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM96006 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users of STAR *
        *                 JOIN in which sparse index is enabled and it *
        *                 uses both in-memory and workfiles for data   *
        *                 probing.                                     *
        ****************************************************************
        * PROBLEM DESCRIPTION: It is possible that a long running      *
        *                      thread may not be cancelled if the      *
        *                      thread is in a loop trying to process   *
        *                      the next record in a Star Join query    *
        *                      which has enabled sparse index access   *
        *                      which uses both in-memory workfile      *
        *                      processing and the workfile database    *
        *                      for data probing.                       *
        ****************************************************************
1       * RECOMMENDATION:                                              *
        ****************************************************************
        A long running thread which is in a loop trying to process the
        next record in a Star Join query, which has enabled sparse index
        access and which uses both in-memory workfile processing and the
        workfile database for data probing, may be difficult to cancel.

        A loop can occur on behalf of a binary search when using the in-
        memory portion of the sparse index.  This problem results when
        the search key to be probed does not exist, but falls within the
        range of the in-memory (workfile) portion of the sparse index.
        The sparse index then performs a binary search trying to return
        the next highest record but the search is incorrect because one
        of the fields used was defined for the workfile binary search
        instead.  So, because of this, the search never completes
        resulting in an infinite loop.
        DB2 has been modified to check if both in-memory and workfiles
        are used for sparse index processing and if a binary search is
        needed for the in-memory portion, the necessary calculations
        will be made instead of using incorrect workfile information.
        This will prevent the loop from occurring.

        Additional keywords: SQLSTARJOIN STARJOIN SQLSPARSEINDEX LOOP
                             SPARSEINDEX INDEXPROBING
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM96006
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNISJNF  PM96006
       DSNISJNN  PM96006
       DSNXROJL  PM96006
       DSNXRT2J  PM96006

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM96006   DSNISJNF DSNISJNN DSNXROJL DSNXRT2J

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNISJNF
       DSNISJNN
       DSNXROJL
       DSNXRT2J

      LISTEND
 UK97630 COVER LETTER END


 UK97669 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89226 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS, DB2 10 for z/OS, and     *
1       *                 DB2 11 for z/OS users of ODBC/CLI.           *
        ****************************************************************
        * PROBLEM DESCRIPTION: SQLCODE -981 when SQLFetchScrol() or    *
        *                      SQLExtendedFetch() is called to         *
        *                      retrieve multiple rows of data with     *
        *                      MULTICONTEXT=1.                         *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        In an ODBC z/OS application that connects to servers that do not
        support multi-row fetch, calling SQLFetchScroll() or
        SQLExtendedFetch() to retrieve multiple rows of data fails with
        SQLCODE -981 when MULTICONTEXT=1.  The context that was
        established for the connection handle was not switched to the
        application causing fetch operation to fail.
        ODBC has been changed to ensure that on each SQLFetchScrol()
        or SQLExtendedFetch() call, the application is switched to
        the correct context that was established for the connection
        handle.
    COMPONENT:  5740-XYR02-JDBAA17
    APARS FIXED: PM89226
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR02 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNAOG26  PM89226
       DSNAOCLI  PM89226
       DSNAOSDK  PM89226

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89226   DSNAOG26 DSNAOCLI DSNAOSDK

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNAOG26
       DSNAOCLI

      MACROS
       DSNAOSDK

      LISTEND
 UK97669 COVER LETTER END


 UK97673 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM91739 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS      *
        *                 users of REORG TABLESPACE utility            *
        ****************************************************************
        * PROBLEM DESCRIPTION: RESTART of a REORG TABLESPACE SHRLEVEL  *
        *                      REFERENCE NOSYSREC on a partitioned     *
        *                      table space caused ABEND0C4 RC11 at     *
1       *                      DSNURPCT + x'126E'                      *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available.         *
        ****************************************************************
        REORG TABLESPACE SHRLEVEL REFERENCE NOSYSREC was run on a
        partitioned table space, which abended in the RELOAD phase. The
        job was restarted, but ABENDS0C4 RC11 at DSNURPCT OFFSET126E
        happened. The problem happened because some internal variables
        for REORG parallelism were not set correctly.

        The problem happens intermittently.  It can also happen with
        universal table spaces (UTS) or with the RESTART of a REORG
        TABLESPACE SHRLEVEL REFERENCE NOSYSREC which abended in the
        SORT, BUILD or SORTBLD phase previously.
        REORG utility has been changed to set the internal variables
        correctly during RESTART.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM91739
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNURFIT  PM91739
       DSNURRNG  PM91739

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM91739   DSNURFIT DSNURRNG

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNURFIT
       DSNURRNG

      LISTEND
 UK97673 COVER LETTER END


 UK97675 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM74776 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users with dynamic       *
        *                 queries.                                     *
        ****************************************************************
        * PROBLEM DESCRIPTION: DB2 incorrectly claims partitions       *
        *                      during prepare of a dynamic query when  *
        *                      probing the index to estimate the       *
        *                      number of qualifying keys.  More        *
        *                      specifically...                         *
        *                       - Claims are taken on unqualified      *
        *                         partitions.                          *
        *                       - Claims are not released until commit *
        ****************************************************************
        * RECOMMENDATION:                                              *
1       ****************************************************************
        During prepare of an SQL statement, DB2 probed the index
        to estimate number of qualifying keys. A claim was acquired on
        the object (table space, index space, partition) and was not
        released until commit.  For a partitioned index, DB2 incorrectly
        acquired claims on all partitions during this index probing.
        For queries with page range screening (PAGE_RANGE='Y' in the
        PLAN_TABLE), claims should not be required on unqualified
        partitions.

        Symptoms of this problem include...

          * Claim/drain contention with DB2 utilities resulting in
            deadlocks and/or timeouts (RC00C200EA, RC00C90088,
            RC00C9008E, RC00C90086).

          * Performance degradation of prepare due to unnecessary
            index probing of unqualified partitions.

        Additional Keywords: SQLACCESSPATH SQLPERFORMANCE

        The following command may be used to determine claims held:
                 -DIS DB(dbname) SP(*) CLAIMERS LIMIT(*)
        DB2 has been updated so that only qualifying index partitions,
        for queries with page range screening (PAGE_RANGE='Y' in
        the PLAN_TABLE) are claimed and processed.  Additionally,
        claim(s) acquired while probing the index are declaimed
        immediately after the probe.

        As with any change to DB2 query optimization that can drive
        a different access path, there is some risk of query performance
        regression.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM74776
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM90116:

        A rebind is necessary for static applications to rebuild
        access paths based on the changes in this APAR.

        PM90116 corrects a problem in which an inefficient access path
        may be selected when statistics in SYSCOLDIST and SYSINDEXES
        are in conflict.

        To make this fix effective for a static application, it must 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 PM88835 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM88835 corrects a problem that the index probing feature may
1       incorrectly set the frequency of the histogram quantiles
        where the histogram statistics are generated for IN-list
        predicates and there is more than 1 quantile generated.

        To make this fix effective for a static application, it must 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
       DSNKCEST  PM74776
       DSNXOGBM  PM74776
       DSNXOIXP  PM74776
       DSNXOPRP  PM74776
       DSNXOPRS  PM74776
       DSNXOTL   PM74776

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM74776   DSNKCEST DSNXOGBM DSNXOIXP DSNXOPRP DSNXOPRS DSNXOTL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNKCEST
       DSNXOGBM
       DSNXOIXP
       DSNXOPRP
       DSNXOPRS
       DSNXOTL

      LISTEND
 UK97675 COVER LETTER END


 UK97692 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM86952 -
        ****************************************************************
        * USERS AFFECTED: All DB2 V10 users                            *
        ****************************************************************
        * PROBLEM DESCRIPTION: (1)                                     *
        *                      Thread 64bit Shared Variable storage    *
        *                      slowly increases over time as observed  *
        *                      in IFCID225 record, field QW0225SV.     *
        *                      (2)                                     *
        *                      ABEND0C4 DSNSVBK when the thread is     *
        *                      canceled while performing contraction   *
        *                      and DSNSCON2 FRR returns to DSNSVBK     *
        *                      with a zero recovery stack pointer.     *
        *                      Since contraction is likely during      *
        *                      a MUST COMPLETE process, DB2 may        *
        *                      terminate.                              *
        *                      (3)                                     *
        *                      DSNSVSVB ABEND04E RC00E2000C when the   *
        *                      thread encounters Pool Full.            *
        ****************************************************************
1       * RECOMMENDATION: Apply apar                                   *
        ****************************************************************
        (1)
        The original design implemented for DB2 storage pool
        contraction, did not include those size slots which contain
        multiple fixed blocks per expansion segment. In analyzing
        various dumps from customers and internal testing, it was
        observed that pools sometimes had significant FREE storage tied
        up in these slots.  By contracting these slots, REAL FRAME usage
        may be reduced since the corresponding virtual storage would be
        available for reuse by other threads, thus not having to back
        additional frames.  Reducing the virtual storage within a given
        pool could potentially prevent requests from being abend04E
        with RC00E2000C, pool full condition.
        (2)
        When a thread attempts to get storage from a pool and finds it
        is full, it will synchronously call contraction for that pool.
        If it is canceled while in the contraction module, that FRR
        recovers but does not handle the recovery stack correctly.
        (3)
        When threads are attempting to get 64bit storage from a system
        level pool and it is full, they will all try to perform
        contraction on that pool but only the one succeeds.  The
        remaining threads are not allowed to wait.  Instead, they
        return and retry their storage request but the pool is
        still full and they abend04E RC00E2000C.
        (1)
        This apar extends the contraction function to include all slot
        sizes, those with multiple blocks per segment and those with one
        block per expansion segment.
        (2)
        Contraction will not retry canceled threads.
        (3)
        Contraction will be serialized and multiple threads contracting
        the same pool, will be allowed to wait while that occurs.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM86952
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNLTMSC  PM86952
       DSNSCON2  PM86952
       DSNSINTM  PM86952
       DSNSSTUP  PM86952
       DSNSVSFB  PM86952
       DSNSVSFM  PM86952
       DSNSVSGM  PM86952
       DSNSVSPP  PM86952
       DSNSVSVB  PM86952
       DSNSVSVP  PM86952
       DSNTXSTB  PM86952

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM86952   DSNLTMSC DSNSCON2 DSNSINTM DSNSSTUP DSNSVSFB DSNSVSFM
1                DSNSVSGM DSNSVSPP DSNSVSVB DSNSVSVP DSNTXSTB

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNLTMSC
       DSNSCON2
       DSNSINTM
       DSNSSTUP
       DSNSVSFB
       DSNSVSFM
       DSNSVSGM
       DSNSVSPP
       DSNSVSVB
       DSNSVSVP
       DSNTXSTB

      LISTEND
 UK97692 COVER LETTER END


 UK97707 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM91639 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS, DB2 10 for z/OS and DB2  *
        *                 11 for z/OS utility users of LOAD FORMAT     *
        *                 INTERNAL                                     *
        ****************************************************************
        * PROBLEM DESCRIPTION: LOAD FORMAT INTERNAL using an input     *
        *                      data set, SYSREC, that is not in        *
        *                      internal format may cause DB2 to crash  *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        LOAD FORMAT INTERNAL using an input data set, SYSREC, that
        contained data that was not in internal format caused DB2 to
        crash.  FORMAT INTERNAL is a performance option that bypasses
        all data validity checks to improve performance and incorrect
        usage may result in numerous types of errors if the procedures
        outlined in the Utility Guide and Reference are not followed.
        To minimize problems caused by usage error, LOAD FORMAT INTERNAL
        will be modified to validate that the actual length of the
        internal format record equals the length specified in the
        internal format record header.
        LOAD FORMAT INTERNAL has been modified to help validate that the
        input data is in fact in internal format by validating the
        actual record length against the length specified in the record
        header.

        Please note no other validity checking of the data will be done
        so users must follow the procedures described in the Utility
        Guide and Reference when using the FORMAT INTERNAL option.

        With this APAR when using the FORMAT INTERNAL option and the
        actual record length does not match the length specified in the
1       record header message MSGDSNU334I will be issued with reason
        code 34 with field-name 'RECORD HEADER LENGTH FOR FORMAT
        INTERNAL' and the job will abend with ABEND04E RC00E40323.

        Example message text for DSNU334I with reason code 34:
        DSNU334I -INPUT FIELD 'RECORD HEADER LENGTH FOR FORMAT INTERNAL'
        INVALID FOR 'table.name' ERROR CODE '34'

        The Messages manual has been changed to add the new reason code
        34 for message DSNU334I:

        DSNU334I csect-name INPUT FIELD field-name INVALID FOR
        table-name, ERROR CODE error-code

        Explanation: The LOAD utility found incorrect input data.

        csect-name:
        The name of the control section that issued the message.

        field-name:
        The name of the field for which incorrect data was provided.

        table-name:
        The name of the table.

        error-code:
        Description of the problem. Possible error codes are:
        01 Input numeric value is out of the range for the table column.
        02 Input numeric field contains invalid numeric data.
        03 An error occurred when converting input numeric data to
        floating-point data.
        04 Input packed decimal data is in error.
        05 Input is too long for a date column.
        06 Input is too short for a date column.
        07 Input is too long for a time column.
        08 Input is too short for a time column.
        09 Input is too long for a timestamp column.
        10 Input is too short for a timestamp column.
        11 Input character field is too long for the table column.
        12 Input variable character field is too long for the table
        column.
        13 Input is out of range for the date/time column.
        14 Input is invalid for the date/time column.
        15 Input length is incorrect for numeric column.
        16 Input contains a blank character.
        17 Input is too long for a graphic column.
        18 Input is invalid for a graphic column.
        19 Input is too long for the table column after a required CCSID
        conversion.
        20 Input contained an invalid code point for a required CCSID
        conversion.
        21 Input does not conform to the rules for valid data for a
        required CCSID conversion.
        22 Input causes an error during CCSID conversion. An example
        of this type of error would be an error
        in a user exit routine.
1       23 Input is invalid for a ROWID column.
        24 Input contained a code point that when translated from the
        source resulted in a substitution character being placed in
        the target string.
        This condition can occur when the NOSUBS keyword was specified
        and no discard data set was specified.
        25 The range of values for an identity column is exhausted.
        26 A null value has been supplied for a not null column.
        27 Input is invalid for a security label column.
        28 Input is a valid security label, but the SECLABEL and the
        user's does not have the authority to load this SECLABEL.
        29 Decimal floating point conversion error.
        31 XML is not well formed.
        >>34 The FORMAT INTERNAL record header length is invalid. 
<<
 

        System action: Further utility processing is terminated.
        User response: Correct the input data and resubmit the job.
        Make sure that the field specification on the LOAD
        statement is consistent with the table definition and the
        input data.
        Correcting this error might mean changing:
        v The table definition
        v The LOAD statement
        v The input data

        Severity: 8 (error)

        Related reference:
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM91639
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DOCUMENTATION:
        ++HOLD DOC changes for APAR PM91639
        The Messages manual has been modified to add reason code
        34 for message DSNU334I to indicate an invalid FORMAT INTERNAL
        record header length.

        Example message text for DSNU334I with reason code 34:
          INPUT FIELD 'RECORD HEADER LENGTH FOR FORMAT INTERNAL' INVALID
          FOR 'SYSADM.TBB' ERROR CODE '34'


        DSNU334I csect-name INPUT FIELD field-name INVALID FOR
        table-name, ERROR CODE error-code

        Explanation: The LOAD utility found incorrect input data.

        csect-name:
        The name of the control section that issued the message.

        field-name:
        The name of the field for which incorrect data was provided.

        table-name:
1       The name of the table.

        error-code:
        Description of the problem. Possible error codes are:
        01 Input numeric value is out of the range for the table column.
        02 Input numeric field contains invalid numeric data.
        03 An error occurred when converting input numeric data to
        floating-point data.
        04 Input packed decimal data is in error.
        05 Input is too long for a date column.
        06 Input is too short for a date column.
        07 Input is too long for a time column.
        08 Input is too short for a time column.
        09 Input is too long for a timestamp column.
        10 Input is too short for a timestamp column.
        11 Input character field is too long for the table column.
        12 Input variable character field is too long for the table
        column.
        13 Input is out of range for the date/time column.
        14 Input is invalid for the date/time column.
        15 Input length is incorrect for numeric column.
        16 Input contains a blank character.
        17 Input is too long for a graphic column.
        18 Input is invalid for a graphic column.
        19 Input is too long for the table column after a required CCSID
        conversion.
        20 Input contained an invalid code point for a required CCSID
        conversion.
        21 Input does not conform to the rules for valid data for a
        required CCSID conversion.
        22 Input causes an error during CCSID conversion. An example
        of this type of error would be an error
        in a user exit routine.
        23 Input is invalid for a ROWID column.
        24 Input contained a code point that when translated from the
        source resulted in a substitution character being placed in
        the target string.
        This condition can occur when the NOSUBS keyword was specified
        and no discard data set was specified.
        25 The range of values for an identity column is exhausted.
        26 A null value has been supplied for a not null column.
        27 Input is invalid for a security label column.
        28 Input is a valid security label, but the SECLABEL and the
        user's does not have the authority to load this SECLABEL.
        29 Decimal floating point conversion error.
        31 XML is not well formed.
        >>34 The FORMAT INTERNAL record header length is invalid. 
<<
 

        System action: Further utility processing is terminated.
        User response: Correct the input data and resubmit the job.
        Make sure that the field specification on the LOAD
        statement is consistent with the table definition and the
        input data.
        Correcting this error might mean changing:
        v The table definition
        v The LOAD statement
1       v The input data

        Severity: 8 (error)

        Related reference:
      ACTION:
        ++HOLD ACT for PM91639:

        This APAR adds a new validity check to check to see if the data
        is in FORMAT INTERNAL prior to load by checking the actual
        record length against the length described in the internal
        format record header and issuing message DSNU334I with reason
        code 34 and ABEND04E RC00E40323 if the values do not match.
        No other data validity checks are being done as part of this
        APAR.

        Example message text for DSNU334I with reason code 34:
          INPUT FIELD 'RECORD HEADER LENGTH FOR FORMAT INTERNAL' INVALID
          FOR 'SYSADM.TBB' ERROR CODE '34'

        Please note that certain editors such as ISPF may strip trailing
        blanks with variable blocked (VB) records if the EDITSET
        'Preserve length' option is not set.   Any editor like ISPF that
        may not honor the existing record length generated by the UNLOAD
        FORMAT INTERNAL may now cause LOAD FORMAT INTERNAL to fail
        this new record length validity check.  Users of FORMAT INTERNAL
        are recommended to not modify the internal format records and
        if editing is necessary it is required that the editor used will
        preserve the VB record length as it is unloaded by the UNLOAD
        FORMAT INTERNAL utility.

        Existing records unloaded with FORMAT INTERNAL that have
        been edited with an editor that does not honor the VB record
        length will need to be unloaded again with UNLOAD FORMAT
        INTERNAL to generate a new SYSREC data set prior to running
        LOAD FORMAT INTERNAL.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNURWBF  PM91639

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM91639   DSNURWBF

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNURWBF

      LISTEND
 UK97707 COVER LETTER END


 UK97760 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM85440 -
        ****************************************************************
1       * USERS AFFECTED: All DB2 for z/OS users of Universal Table    *
        *                 Space (UTS) and Classic-Partitioned Table    *
        *                 Space                                        *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C90101 in DSNIDBDF with    *
        *                      ERQUAL5222 during DBET Notify Exit      *
        *                      processing, followed by DB2 coming down *
        *                                                              *
        *                      ABEND04E RC00C90101 in DSNIDBEL with    *
        *                      ERQUAL5222 during DBET Notify Exit      *
        *                      processing                              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        During DBET Notify Exit processing, the following abends may be
        encountered when processing a large number of partitions in an
        exception state, where some or all of these partitions have
        piece level information on them:

        ABEND04E RC00C90101 in DSNIDBDF with ERQUAL5222 and DB2 going
        down (crash)
         - where local DBET is out of synch with SCA

        ABEND04E RC00C90101 in DSNIDBEL with ERQUAL5222
         - where local DBET includes a partition range with piece level
           information

        When collapsing DBET entries with the same restrictive or
        advisory states in a DBET block, the entries can move from
        one DBET block to another.  An entry that has moved can
        contain piece level information.  However, a flag to indicate
        that the DBET block includes an entry with piece information is
        not updated properly.

        Further investigation showed that the incorrectly set flag can
        cause local DBET to be built incorrectly later on.
        DB2 has been modified to correctly set the flag in question.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM85440
    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  PM85440
       DSNIDBEL  PM85440
       DSNIDBGC  PM85440
       DSNIDBHK  PM85440
       DSNIDBMF  PM85440
       DSNIDBMS  PM85440
       DSNIDBPX  PM85440
       DSNIDBSE  PM85440

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM85440   DSNIDBAB DSNIDBEL DSNIDBGC DSNIDBHK DSNIDBMF DSNIDBMS
                 DSNIDBPX DSNIDBSE
1
      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIDBAB
       DSNIDBEL
       DSNIDBGC
       DSNIDBHK
       DSNIDBMF
       DSNIDBMS
       DSNIDBPX
       DSNIDBSE

      LISTEND
 UK97760 COVER LETTER END


 UK97770 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM95403 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS, DB2 10 for z/OS and      *
        *                 DB2 11 for z/OS users of REORG SHRLEVEL      *
        *                 CHANGE.                                      *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C90101 at DSNILREP:5399    *
        *                      during the LOG phase of a REORG         *
        *                      TABLESPACE SHRLEVEL CHANGE.             *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available.         *
        ****************************************************************
        A REORG TABLESPACE SHRLEVEL CHANGE ran on a table space with
        concurrent updates.  The REORG abended with ABEND04E RC00C90101
        at DSNILREP ERQUAL5399 during the LOG apply phase.
        This problem occurred because some log information which was
        needed to apply was lost during the log record processing
        because of the storage boundary.
        REORG code has been modified to resolve the aforementioned
        problem.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM95403
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUGLGR  PM95403

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM95403   DSNUGLGR

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUGLGR

1     LISTEND
 UK97770 COVER LETTER END


 UK97828 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM95289 -
        ****************************************************************
        * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
        *                 DB2 10/11 for z/OS only.                     *
        ****************************************************************
        * PROBLEM DESCRIPTION: Message DSNL027I THREAD-INFO message    *
        *                      displays incorrectly if the primary     *
        *                      authorization ID value contains the     *
        *                      '#' character.                          *
        *                      For example:                            *
        *                       DSNL027I ... DISTRIBUTED AGENT WITH    *
        *                        LUWID=luw-id                          *
        *                        THREAD-INFO=ADMF                      *
        *                       01:*:*:*:*:*:*:*                       *
        *                        RECEIVED ABEND=abend                  *
        *                        FOR REASON=reason                     *
        *                      where primary auth ID = ADMF#01         *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        DB2 message DSNL027I may display the THREAD-INFO text
        incorrectly if the value of the primary authorization ID
        associated with the thread contains a '#' character. The
        THREAD-INFO text displays incorrectly because DB2 uses the '#'
        character as the new-line character for this message.
         NOTE: The problem only applies to DB2 10/11 for z/OS.
          The problem does not affect DB2 9 for z/OS or earlier users.
          This is because DB2 10 for z/OS modified the attributes of
          the DSNL027I message in order to accommodate a new component
          of the THREAD-INFO text.

        DB2 10/11 for z/OS have been changed to use a different
        new-line character for formatting the DSNL027I message so that
        the use of the '#' character for the primary authorization ID
        will be displayed correctly.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM95289
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNFLDIR  PM95289
       DSNFMDIR  PM95289

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM95289   DSNFLDIR DSNFMDIR

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

1     MODULES
       DSNFLDIR
       DSNFMDIR

      LISTEND
 UK97828 COVER LETTER END


 UK97861 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM93460 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS, DB2 10 for z/OS and      *
        *                 DB2 11 for z/OS utility users of the         *
        *                 LOAD utility with LOB columns                *
        ****************************************************************
        * PROBLEM DESCRIPTION: LOAD abended with ABEND0C4 at DSNOGETD  *
        *                      +x'28d8' when loading a NOT NULL WITH   *
        *                      DEFAULT LOB column                      *
        ****************************************************************
        * RECOMMENDATION: Apply corrective when available              *
        ****************************************************************
        LOAD abended with ABENDS0C4 at DSNOGETD OFFSET28D8 when
        loading a default value for NOT NULL WITH DEFAULT LOB
        column.  The utility incorrectly tried to load data
        into the LOB table space even though the default value
        was already loaded.
        The LOAD utility has been changed to fix the reported problem.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM93460
    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  PM93460
       DSNURWBG  PM93460

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM93460   DSNURWBF DSNURWBG

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNURWBF
       DSNURWBG

      LISTEND
 UK97861 COVER LETTER END


 UK97873 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM89391 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 for zOS                     *
1       *                                                              *
        ****************************************************************
        * PROBLEM DESCRIPTION: An agent may become hung in CSECT       *
        *                      DSNTABA if a -CANCEL THREAD command is  *
        *                      issued for that agent while it was      *
        *                      holding an IRLM lock.                   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When a -CANCEL THREAD command is issued for an agent that is
        holding a SKPT p-lock, EDM abort processing will save that
        SKPT p-lock on a global EDM chain to be cleaned up during IRLM
        synchronization that occurs during general agent abort/
        deallocation processing.  Any new agent that requires the same
        SKPT p-lock may also try to purge SKPT p-locks on the global
        EDM chain that are leftover from previous threads.

        This leads to a race condition between IRLM synchronization
        process for a cancelled thread an a new DB2 agent that may be
        interested in the SKPT p-lock.  If the latter wins the race,
        IRLM synchronization processing in CSECT DSNTABA will
        incorrectly suspend waiting for a system task that its scheduled
        to free the lock.  This will never occur since this system task
        will not find this lock, resulting in a indefinite hang in the
        CSECT DSNTABA.

        This race condition only exists when SKPT p-lock is involved.
        Remove the race condition by having EDM cancel processing use
        an agent specific chain to save those SKPT p-locks that need to
        be freed during the abort/deallocation process.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM89391
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNGEELC  PM89391
       DSNGEFLC  PM89391
       DSNTABA   PM89391
       DSNTADL   PM89391

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM89391   DSNGEELC DSNGEFLC DSNTABA  DSNTADL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNGEELC
       DSNGEFLC
       DSNTABA
       DSNTADL

      LISTEND
 UK97873 COVER LETTER END

1
 UK97902 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM93381 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS 9, 10 and 11 users who      *
        *                 use XMLPARSE with an argument XML host       *
        *                 variable.                                    *
        ****************************************************************
        * PROBLEM DESCRIPTION: An incorrect SQLCODE -171 occurs on     *
        *                      XMLPARSE with an argument XML host      *
        *                      variable.                               *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An incorrect SQLCODE -171 occurs on an SQL statement that
        contains XMLPARSE whose argument is an XML host variable.

        A sample of such an SQL statement may be:

        INSERT INTO TABLE T(C)
        VALUES(XMLPARSE(DOCUMENT :xmlhv));

        SQLCODE -171 is erroneously issued when the statement is bound
        or prepared.

        The SQLCA may show DSNXOBFF raising the SQLCODE
        with SQLERRD1=149.
        DB2 code is modified to not issue SQLCODE -171.

        ADDITIONAL KEYWORDS: XMLPARSE SQLHOSTVARIABLE SQLHOSTVAR
                             SQLCODE171
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM93381
    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  PM93381
       DSNNOPAR  PM93381
       DSNXOBFF  PM93381
       DSNXOSCF  PM93381

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM93381   DSNNOIRT DSNNOPAR DSNXOBFF DSNXOSCF

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNNOIRT
       DSNNOPAR
       DSNXOBFF
       DSNXOSCF

      LISTEND
1UK97902 COVER LETTER END


 UK97939 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM94158 -
        ****************************************************************
        * USERS AFFECTED:  All DB2 for z/OS version 9 and DB2 for      *
        *                  z/OS version 10 and DB2 for z/OS version    *
        *                  11 users of SQL statements containing the   *
        *                  LIKE predicate with RTRIM/STRIP FUNCTION    *
        *                  and a literal pattern with blank            *
        *                  characters.                                 *
        ****************************************************************
        * PROBLEM DESCRIPTION: Incorrect output may be returned when   *
        *                      query satisfies all of the following    *
        *                      conditions:                             *
        *                      1 Contains the LIKE predicate.          *
        *                      2 Contains RTRIM FUNCTION or STRIP      *
        *                        FUNCTION whose second parameter is    *
        *                        trailing and strip character is not   *
        *                        specified on the column.              *
        *                      3 Has blank characters preceding a      *
        *                        wild card character at the end of     *
        *                        the literal pattern.                  *
        *                      4 There is an index on the column.      *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Incorrect output may be returned when query satisfies all of
        the following conditions:
        1 It contains LIKE predicate.
        2 It contains RTRIM FUNCTION or STRIP FUNCTION whose second
          parameter is trailing and strip character is not specified
          on column.
        3 There is blank character right before wild card character
          at the end of literal pattern.
        4 There is an index on the column.

        An example for incorrect output is shown below:

        CREATE TABLE TABLIKE(C1 CHAR(10),C2 CHAR(2));
        INSERT INTO TABLIKE VALUES('ZBDX','ZQ');
        CREATE INDEX IDXC1 ON TABLIKE(C1);

        SELECT C1
        FROM TABLIKE
        WHERE RTRIM(C1) LIKE 'ZBDX %';

        OR

        SELECT C1
        FROM TABLIKE
        WHERE STRIP(C1,T) LIKE 'ZBDX %';


1

        DB2 did not correctly process the aforementioned SQL
        statements, which caused incorrect output.

        SOLUTION:
        DB2 has been modified to correctly process the aforementioned
        SQL statement,so there will be no incorrect output.

        Additional Keywords:  SQLINCORR SQLINCORROUT DB2INCORR/K
                              SQLLIKE  SQLINDEX
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM94158
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        PM94158 corrects a problem of incorrect output returned
        when query contains LIKE predicate with RTRIM/STRIP
        FUNCTION and literal pattern with blank pattern and
        index created on column in RTRIM/STRIP.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOBM   PM94158

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM94158   DSNXOBM

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOBM

      LISTEND
 UK97939 COVER LETTER END


 UK97981 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM94539 -
        ****************************************************************
        * USERS AFFECTED: All HIR2220(IRLM 2.2) and HIR2230(IRLM 2.3)  *
        *                 users of data sharing SYSPLEXDS who have     *
        *                 PM65217 (PTFs UK79710/UK79709) applied.      *
        ****************************************************************
        * PROBLEM DESCRIPTION: Sysplex wide hang may occur when        *
        *                      multiple DB2/IMS members are restarted  *
        *                      at the same time, or a group restart,   *
        *                      and if IRLM lock structure rebuild is   *
        *                      triggered in between for any reason.    *
        *                      Lock structure rebuild gets hung.       *
        *                      MSGIXL041E issued for delay in response *
        *                      for XES Failconn event.                 *
        *                      ABEBDS026 dump is also taken by XES for *
        *                      IRLM connector which did not respond.   *
        *                      MVS may terminate non-responding IRLM   *
1       *                      causing DB2 to terminate as well.       *
        ****************************************************************
        * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
        ****************************************************************
        During restart of multiple DB2/IMS members, an IRLM may trigger
        the lock rebuild for co-existence when his IRLM function level
        is lower than the function level of the existing IRLMs in the
        group. The lock structure rebuild may also get started for other
        reasons as well (for maxuser, restart query, structure failure).
        There is a timing error in IRLM handling XES events for member
        disconnect that may happen while the lock structure is being
        quiesced for rebuild. IRLMs receiving the failed connection
        event may not process these events correctly and not send a
        response to XES for the failed connection event. This can leave
        XES waiting for IRLM response and surviving IRLMs participating
        in the rebuild waiting for next rebuild event from XES
        a deadlock situation causing the whole datasharing group hang.
        MSGIXL041E for IRLM CONNECTOR NAME:xxxxxxxx  which has not
        responded to the DISCONNECTED/FAILED connection vent, is issued.
        MVS also issues ABEND=S026,REASON=08118001,CONNECTOR HANG for
        the hung connector.
        During Rebuild if we get Failconn event for a member A
        while IRLM serialization (RLMFENCE) was held at that time
        to process global initialization for a member B, IRLM will
        queue the Failconn event processing (qe0507) for member A
        on its work-todo-queue instead of putting it on rebuild
        pending queue (RLMRBPQE). This will enable the Failconn
        event to be processed before the rebuild. IRLM will issue
        the Failconn event response that XES would be waiting on
        in order to first complete the connection cleanup for the
        lost member.
    COMPONENT:  5695-16401-HIR2230
    APARS FIXED: PM94539
    SPECIAL CONDITIONS:
      COPYRIGHT: 5695-16401 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DXRRL2R4  PM94539
       DXRRL710  PM94539
       DXRRL752  PM94539

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM94539   DXRRL2R4 DXRRL710 DXRRL752

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DXRRL2R4
       DXRRL710
       DXRRL752

      LISTEND
 UK97981 COVER LETTER END


1UK98030 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM94353 -
        ****************************************************************
        * USERS AFFECTED: All users with data replication products.    *
        ****************************************************************
        * PROBLEM DESCRIPTION: New function to create a new database   *
        *                      restrictive state that sets read only   *
        *                      for most applications while allowing    *
        *                      replication products write to update.   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The -START DATABASE command is enhanced to allow a new ACCESS
        keyword of RREPL to permit read only access to the data except
        by applications designated as a replication product. RRS attach
        is enhanced with a new function of 'SET_REPLICATION' to identify
        to DB2 that the application is a replication product. This
        function is restricted to only supervisor state and APF
        authorized programs - that is, an application link edited as
        AC(1) and residing in an APF authorized library or that is
        running supervisor state as indicated by the PSW.  An attempt to
        invoke the 'SET_REPLICATION' function will result in a abend
        with reason code 00C12035 if not properly authorized.
        Applications not designated as a replication product which
        attempt to perform an insert, update, or delete will receive a
        resource unavailable error with a reason code of 00C90224.
        Utilities will behave as with status RO but with the new reason
        code for the resource unavailable.
        RC00C12035 RC00C90224

        See the ++HOLD(DOC) for detailed information.
        New function enablement.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM94353
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DOCUMENTATION:
        This is the enabling apar for PM90970.
        PM90970 must be applied to all members of a data sharing group
        before applying PM94353.

        The -START DATABASE command is enhanced to allow a new ACCESS
        keyword of RREPL to permit read only access to the data except
        by applications designated as a replication product. RRS attach
        is enhanced with a new function of 'SET_REPLICATION' to identify
        to DB2 that the application is a replication product. This
        function is restricted to only supervisor state and APF
        authorized programs - that is, an application link edited as
        AC(1) and residing in an APF authorized library or that is
        running supervisor state as indicated by the PSW.  An attempt to
        invoke the 'SET_REPLICATION' function will result in a abend
        with reason code 00C12035 if not properly authorized.
        Applications not designated as a replication product which
        attempt to perform an insert, update, or delete will receive a
1       resource unavailable error with a reason code of 00C90224.
        Utilities will behave as with status RO but with the new reason
        code for the resource unavailable.

        SET REPLICATION function for RRSAF

        The RRSAF SET_REPLICATION function enables an APF authorized
        program to identify to DB2 as a replication program. Calling the
        SET_REPLICATION function is optional. If you do not call it, DB2
        treats the application normally. The SET_REPLICATION function
        allows the application to perform insert, update, and delete
        operations when the tablespace or database is started access
        RREPL.

        The following diagram shows the syntax of the SET REPLICATION
        function.

        DSNRLI SET_REPLICATION function

        >>--CALL DSNRLI------------------------------------------->
        >-(--function--+------------------------------------+--)--><
                       '--,--retcode--+----------------+--'
                                      '--,--reascode--'

        Parameters point to the following areas:
        function
        An 18 byte area that contains SET_REPLICATION
        retcode
        A 4-byte area in which RRSAF places the return code.
        This parameter is optional. If you do not specify retcode, RRSAF
        places the return code in register 15 and the reason code in
        register 0.
        reascode
        A 4-byte area in which RRSAF places the reason code.

        This parameter is optional. If you do not specify reascode,
        RRSAF places the reason code in register 0.

        If you specify reascode, you must also specify retcode.

        -DISPLAY DATABASE Syntax

                        +--,------------+
                        v               |
        >--RESTRICT--(-----+---------+--+--)--><
                           |--ACHKP--|
                           |--CHKP---|
                           |--COPY---|
                           |--GRECP--|
                           |--LPL----|
                           |--RBDP---|
                           |--RECP---|
                           |--REORP--|
                           |--RO-----|
                           |--RREPL--|
                           |--STOP---|
1                          |--UT-----|
                           |--UTRO---|
                           |--UTRW---|
                           |--UTUT---|
                           |--UT*----|
                           '--WEPR---'


        RESTRICT

        Limits the display to databases, table spaces, or indexes in a
        restricted status. This includes those page sets that have
        logical page list entries. Specifying one or more keywords
        further limits the display to the named objects only.

        Abbreviation: RES

        Use of a database is restricted if the database is in any of the
        following situations:
        It is started for read-only processing.
        It is started for read or replication only processing.
        It is started for utility-only processing.
        It is stopped.

        Use of a table space or index space is restricted if the table
        space or index space is in any of the following situations:
        It is in one of the three situations listed previously.
        It is being processed by a utility.
        It is in COPY-pending, CHECK-pending, RECOVER-pending, group
        buffer pool RECOVER-pending, auxiliary CHECK-pending, or
        REORG-pending status.
        It contains a page error range.
        It contains pages in the logical page list (LPL).

        Specify one or more of the following keywords to limit objects
        that are to belisted.
        ACHKP
        Displays objects in the auxiliary warning advisory state.
        CHKP
        Display objects that are in CHECK-pending status.
        COPY
        Display objects that are in COPY-pending status.
        GRECP
        Displays objects that are in group buffer pool RECOVER-pending
        status.
        LPL
        Displays logical page list entries.
        RBDP
        Displays index objects that are in REBUILD- or RECOVER-pending
        status. This includes the restricted states RBDP, RBDP*, PSRBDP,
        LPL, and WEPR.
        RECP
        Displays objects that are in RECOVER-pending status, including
        the restricted states RECP, RECP*, LPL, and WEPR (write error
        page range).
        REORP
1       Displays objects that are in REORG-pending status.
        RO
        Displays objects that are in read-only mode.
        RREPL
        Displays objects that are in read and replication only mode.
        STOP
        Displays objects that are stopped, including the restricted
        states STOP, STOPE, STOPP, and LSTOP.
        UT
        Displays objects that are in utility access mode.
        UTRO
        Display objects that are serialized for utility access and
        available for read-only access.
        UTRW
        Display objects that are serialized for utility access and
        available for read-write access.
        UTUT
        Displays objects that are serialized for utility access and
        unavailable.
        UT*
        Displays objects that are in any utility access mode: UT, UTRW,
        UTRO, or UTUT.
        WEPR
        Displays write error page range information.

        -START DATABASE Syntax

                      .--RW-----.
        >--ACCESS--(--+--RO-----+--)--><
                      |--UT-----|
                      |--RREPL--|
                      '--FORCE--'

        Option descriptions

        ACCESS

        Specifies whether the objects that are started are in read/write
        read only, or utility only status. Also forces access to objects
        that are in unavailable status.

        Abbreviation: ACC

        (RW)
        Allows programs to read from and write to the specified
        databases, table spaces, indexes, or partitions.
        (RO)
        Allows programs to only read from the specified databases, table
        spaces, indexes, or partitions. Any programs attempting to write
        to the specified objects will not succeed. Do not use this
        option for a database for declared temporary tables (databases
        created with the AS TEMP option).
        (UT)
        Allows only DB2 online utilities and the SQL DROP statement to
        access the specified databases, table spaces, indexes, or
        partitions.
1       (RREPL)
        Allows programs to only read from the specified databases, table
        spaces, indexes, or partitions unless they have identified as a
        replication program. Any other programs attempting to write to
        the specified objects will not succeed. Do not use this option
        for a database for declared temporary tables (databases created
        with the AS TEMP option).

        Note: If RREPL is specified in V10 CM or V10 ENFM it will be
        converted to RO and no message will be issued.
        (FORCE)
        Resets any indications that a table space, index, or partition
        is unavailable because of pages in the logical page list,
        pending-deferred restarts, write-error ranges, read-only
        accesses, or utility controls. FORCE also resets the
        CHECK-pending, COPY-pending, and RECOVER-pending states. Full
        access to the data is forced. FORCE cannot be used to reset the
        restart-pending (RESTP) state.

        When using ACCESS(FORCE), you must use a single database name,
        the SPACENAM option, and an explicit list of table space and
        index names. You cannot use any range or combination of pattern-
        matching characters (*), including DATABASE (*) or SPACENAM (*).

        A utility-restrictive state is reset (and the utility is
        terminated) only if all of the target objects are reset with
        this command. To identify which objects are target objects of
        the utility, use the DISPLAY DATABASE command, or run the
        DIAGNOSE utility with the DISPLAY SYSUTIL option. The DIAGNOSE
        utility should be used only under the direction of IBM Software
        Support.

        Note: ACCESS(FORCE) will not successfully complete if the object
        you are trying to force was placed in a utility-read-only (UTRO)
        utility-read-write (UTRW), or utility-utility (UTUT) state by a
        utility running in a previous release of DB2. If this situation
        is encountered, DB2 issues message DSNI041I. To reset the
        restrictive state, you must terminate the utility using the
        release of DB2 in which it was started.

        A table space or index space that is started with ACCESS(FORCE)
        might be in an inconsistent state.

        New Codes:

        00C12035

        Explanation: The DB2 RRSAF attachment facility function
        SET_REPLICATION was invoked by a program that was not APF
        authorized or was not running in supervisor state. This
        condition can indicate a security violation.

        System action: The application is abended.

        User response: The SET_REPLICATION function can only be invoked
        from an APF authorized or supervisor state program. Contact your
1       security administrator to make the changes required to make your
        program an APF authorized program or to have your program run in
        supervisor state.

        Problem determination:

        00C90224

        Explanation: An attempt was made to allocate a resource for
        update operations. However, the resource was already started for
        read and replication only access.

        System action: The allocation process is not allowed.

        Operator response: If this reason code appears in message
        DSNT501I, determine whether the named resource should be started
        for read and replication only access.

        User response: Determine when the resource is started for
        read/write access, and rerun the job.

        Problem determination: The requested operation is not performed.
        An SQLCODE -904 is issued, and/or message DSNT501I is issued.
        For more information, refer to the SQL return code in Codes, or
        to the description of the DSNT501I message in Messages.
      ACTION:
        DSNTIJUZ must be run to reassemble the system parameters
        module (DSNZPARM by default) to pick up changes to DSN3DIR1.

        This is the enabling APAR for PM90970.
        The PTF for APAR PM90970 must be applied to all members
        of a DB2 V10 data sharing group before applying the
        PTF for this APAR PM94353 and exploiting RREPL.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNARA00  PM94353
       DSNARA70  PM94353
       DSN3AMGP  PM94353
       DSN3AMI1  PM94353
       DSN3AM00  PM94353
       DSN3DIR1  PM94353
       DSN3RR30  PM94353
       DSN3SSIN  PM94353
       DSN9SCNA  PM94353
       HDBAA10J  PM94353

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM94353   DSNARA00 DSNARA70 DSN3AMGP DSN3AMI1 DSN3AM00 DSN3DIR1
                 DSN3RR30 DSN3SSIN DSN9SCNA HDBAA10J

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNARA00
       DSNARA70
       DSN3AMGP
1      DSN3AMI1
       DSN3AM00
       DSN3DIR1
       DSN3RR30
       DSN3SSIN
       DSN9SCNA

      LISTEND
 UK98030 COVER LETTER END


 UK98047 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM97071 -
        ****************************************************************
        * USERS AFFECTED: Users of the DSNTIJEN job for DB2 10 for     *
        *                 z/OS.                                        *
        ****************************************************************
        * PROBLEM DESCRIPTION: Broken directory database data can      *
        *                      cause problems during the DB2 10 for    *
        *                      z/OS ENFM process.                      *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        Invalid length data in the DBD01 directory table space for a
        database can lead to lost database data during ENFM processing.

        When processing DBD01 table space rows ENFM processing relies
        on length data to determine how data should be merged up to form
        the BLOB that is being created. In the reported case the length
        value was twice what it should have been and so the ENFM process
        continued to merge up BLOB data. The additional bytes merged
        into the BLOB value came from other database rows. This
        effectively lost the database information for those databases
        that were merged into the BLOB.

        In the reported scenario DSNDB06 was one of the databases
        'lost' during the ENFM process and this disabled the DB2
        subsystem.
        DB2 ENFM processing code has been changed so that it will now
        detect the invalid DBD length situation. If the ENFM process
        determines that there is a DBD length problem then it will issue
        a DSNU777I message that indicates the name of the broken
        database as follows:

          DSNU777I  DSNUECML - REORG ENFM STATUS -
                    DETECTED BROKEN DATABASE DURING ENFM - dbname

        The ENFM process will then abend (REASON=X'00E40600') to prevent
        any damage from being done to the directory data and subsystem.

        Additional keywords: ABEND04E RC00E40600 MSGDSNU777I
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM97071
    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
       DSNUECML  PM97071

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM97071   DSNUECML

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUECML

      LISTEND
 UK98047 COVER LETTER END


 UK98065 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM97565 -
        ****************************************************************
        * USERS AFFECTED: All DB2 users.                               *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND0C4 IN DSNIRCSB+31F2 DURING DB2    *
        *                      RESTART.                                *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        During DB2 restart, if Data Manager (DM) sees multiple
        checkpoint LRs for the same linear page set (table space or
        index space), it incorrectly references the Data Base Restart
        Table (DBRT) entry for that linear page set. This results in
        address exception when trying to reference storage which is
        beyond the size of the DBRT entry. The DM restart code logic
        will make sure that for linear page set it should not reference
        any entry beyond the first entry in the table.
        Data Manager restart logic is corrected to calculate the correct
        indexing for linear page set to avoid this addressing exception
        error.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM97565
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNIRCSB  PM97565

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM97565   DSNIRCSB

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIRCSB

1     LISTEND
 UK98065 COVER LETTER END


 UK98072 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM96389 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS utility users of REORG   *
        *                 TABLESPACE on table spaces with HASH         *
        *                 organization.                                *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00E40405 and MSGDSNT500I     *
        *                      RC00C200E2 during REORG TABLESPACE      *
        *                      SHRLEVEL CHANGE PART(m,n) of a table    *
        *                      space organized by HASH.                *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        User ran a REORG TABLESPACE SHRLEVEL CHANGE PART (m,n) against
        a table space with hash organization.  The REORG abended with
        an ABEND04E RC00E40405 and DSNT500I RESOURCE UNAVAILABLE with
        RC00C200E2.  The resource identified was a partition of the
        table space that was not part of the REORG.

        A REORG on a disjoint partition range of a table space with
        HASH organization was attempting to serialize a partition
        that was not part of the disjoint partition range.
        REORG code has been modified to identify the correct partitions
        in the disjoint partition range specified.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM96389
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNURFIT  PM96389

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM96389   DSNURFIT

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNURFIT

      LISTEND
 UK98072 COVER LETTER END


 UK98085 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM93461 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS, DB2 10 for z/OS and      *
1       *                 DB2 11 for z/OS users of REORG TABLESPACE    *
        *                 SHRLEVEL CHANGE utility.                     *
        ****************************************************************
        * PROBLEM DESCRIPTION: REORG TABLESPACE SHRLEVEL CHANGE on an  *
        *                      entire partitioned-by-growth ( PBG )    *
        *                      table space failed with ABEND04E        *
        *                      RC00E4D5D2 DSNURLAP OFFSET5114 in the   *
        *                      LOG phase due to processing of update   *
        *                      log records that were not fully-logged  *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        User ran a REORG TABLESPACE SHRLEVEL CHANGE on an entire
        partitioned-by-growth (PBG) table space, where new partitions
        were grown during REORG execution.  REORG issued the ABEND04E
        RC00E4D5D2 at DSNURLAP + x'5114' in the LOG phase when it
        encountered an update log record from one of the newly grown
        partitions, because the update log records being applied were
        not fully-logged despite REORG expecting them to be.

        The reported problem was caused by an incorrect program logic
        where REORG did not turn on full logging at the page set level,
        which would be inherited by newly grown PBG partitions.  Full
        logging is currently only turned on for existing partitions at
        the start of the REORG.

        A similar issue exists for DB2 9 and DB2 10, which can result
        in other external symptoms including storage overlay and/or
        broken data when REORG applies the non-fully-logged update log
        records incorrectly.

        Additional keywords :
        - DB2OVRLAY DB2OVRLAY-K DB2OVRLAY-M DB2OVRLAY-N
        Code has been modified for REORG TABLESPACE SHRLEVEL CHANGE to
        turn on full-logging at the pageset level when needed on a PBG
        table space, which will address the aforementioned scenario
        with the newly grown partitions inheriting this full log
        attribute at creation time.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM93461
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNURDRN  PM93461
       DSNURLOG  PM93461

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM93461   DSNURDRN DSNURLOG

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNURDRN
       DSNURLOG
1
      LISTEND
 UK98085 COVER LETTER END


 UK98116 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM90435 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS data sharing users of       *
        *                 group restart where the SCA structure is     *
        *                 rebuilt                                      *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00C90101 DSNISREC ERQUAL5009 *
        *                      may occur during GRECP recovery when    *
        *                      the GRECP state should not be on to     *
        *                      begin with (was resolved earlier)       *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        In a scenario where the GRECP condition exists, followed by
        GRECP being resolved (e.g. via -START DATABASE SPACENAM),
        followed by a group restart where SCA is rebuilt, the GRECP
        condition may mistakenly reappear in the DBET structure during
        the group restart even though it has already been recovered.

        This reappearance of GRECP is not the real GRECP, given that it
        is not accompanied by typical GRECP-related messages such as
        MSGDSNB320I, MSGDSNB321I, MSGDSNB322I or MSGDSNB323I. The GRECP
        state is only reflected in the internal DBET structure and in
        the -DISPLAY DATABASE output.

        The reason for this problem is that group restart log apply may
        incorrectly process DBET logs during Current Status Rebuild
        (CSR), specifically the GRECP removal log record written during
        the -START DATABASE SPACENAM recovery that took place during
        mainline.

        The "fake" reappearance of GRECP may result in the 
DSNISREC:5009
 
        abend when an attempt is made to recover the object for a second
        time. If the problem occurs before  this APAR is applied, the
        incorrect GRECP state may be removed via -START DATABASE
        SPACENAM ACCESS(FORCE).
        Code has been modified to correctly apply the logs during group
        restart.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM90435
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNIDBMS  PM90435

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM90435   DSNIDBMS
1
      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIDBMS

      LISTEND
 UK98116 COVER LETTER END


 UK98135 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM94696 -
        ****************************************************************
        * USERS AFFECTED: All DB2 dynamic statement cache users with   *
        *                 SQL statement section size greater than 65K  *
        ****************************************************************
        * PROBLEM DESCRIPTION: Users may receive the following         *
        *                      ABND0C4 RC0000003B at DSNGEPLC+9014.    *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        When running a dynamic statement SQL with the dynamic statement
        cache enabled, DB2 stores the SQL section in the dynamic
        statement cache pool. An incorrect size is used to acquire the
        storage. If the SQL statement has a section size over 65K, an
        overlay could occur.
        DB2 has been changed to acquire the correct storage to prevent
        the overlay.

        Additional keywords: DB2OVRLAY/K SQLDYNSTMTCACHE SMCOVERLAY
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM94696
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        After appying the apar, rebind all the packages found by the
        following query.
        SELECT NAME, RELEASE FROM SYSIBM.SYSPACKAGE WHERE
          RELEASE = 'I';
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNGECMP  PM94696
       DSNGEDLC  PM94696
       DSNGEELC  PM94696
       DSNGEFBK  PM94696
       DSNGEFLC  PM94696
       DSNGEFSP  PM94696
       DSNGEGBK  PM94696
       DSNGEGFB  PM94696
       DSNGEGSK  PM94696
       DSNGEINT  PM94696
       DSNGEPIS  PM94696
       DSNGEPLC  PM94696
       DSNGERBK  PM94696
1      DSNGESLC  PM94696
       DSNGEZPM  PM94696
       DSNTFDMP  PM94696
       DSNWDFSM  PM94696

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM94696   DSNGECMP DSNGEDLC DSNGEELC DSNGEFBK DSNGEFLC DSNGEFSP
                 DSNGEGBK DSNGEGFB DSNGEGSK DSNGEINT DSNGEPIS DSNGEPLC
                 DSNGERBK DSNGESLC DSNGEZPM DSNTFDMP DSNWDFSM

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNGECMP
       DSNGEDLC
       DSNGEELC
       DSNGEFBK
       DSNGEFLC
       DSNGEFSP
       DSNGEGBK
       DSNGEGFB
       DSNGEGSK
       DSNGEINT
       DSNGEPIS
       DSNGEPLC
       DSNGERBK
       DSNGESLC
       DSNGEZPM
       DSNTFDMP
       DSNWDFSM

      LISTEND
 UK98135 COVER LETTER END


 UK98147 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM94641 -
        ****************************************************************
        * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
        ****************************************************************
        * PROBLEM DESCRIPTION: The following symptoms are reported:    *
        *                      1.ABND=0C4-00000038,                    *
        *                        LOC=DSNLILLM.DSNLCCLO+3288            *
        *                      2.ABND=04E-00D30112,                    *
        *                        LOC=DSNLILLM.DSNLCICF:0014            *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The following problems are reported:
        1. DB2 for z/OS requester processing encountered an error while
           parsing user data containing LOBs and hence tried to flush
           the LOBs off the network. The communication buffer had to be
           extended in order to receive the flushed LOB, after which
           requester processing incorrectly tried to reference an
           output buffer which did not exist since there was no data to
1          return. The reference to the non existent buffer causes the
           reported abend.
        2. A remote client tried to negotiate DRDA encryption with a
           DB2 for z/OS server but the DB2 server failed to set up
           encryption due to an unavailable resource. This causes
           a DSNL045I, and in some cases a DSNL046I, message to be
           issued. However, if an internal serviceability IFCID trace
           event is enabled, DB2 incorrectly provides a dump to reflect
           the condition.

        DB2 is changed as follows:
        1. DB2 for z/OS requester processing has been changed to not
           reference a non existent output buffer when flushing LOBs
           off the network after extending the communication buffer.
        2. DB2 for z/OS server processing has been changed to no longer
           provide a serviceability dump when a DSNL045I or DSNL046I
           message is issued since the condition does not reflect an
           actual error.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM94641
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNLCCLO  PM94641
       DSNLCICF  PM94641

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM94641   DSNLCCLO DSNLCICF

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNLCCLO
       DSNLCICF

      LISTEND
 UK98147 COVER LETTER END


 UK98150 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM91751 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS user running DSN1LOGP       *
        *                 with the CHECK(DATA) option                  *
        ****************************************************************
        * PROBLEM DESCRIPTION: A false detection of page regression    *
        *                      when page size is 32K                   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The log record for 32K page size requires two log records
        to store the full page information. In this case, the previous
        LRSN in the 2nd log record is not reset with the new LRSN
1       of the first log record that was written.  As a result, false
        page regression is detected  when running DSN1LOGP with the
        CHECK(DATA) option.
        This serviceability apar is created to modify DB2 code
        to update the previous page LRSN/RBA on the log record
        accordingly.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM91751
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNIDLOD  PM91751
       DSNIFOD   PM91751
       DSNIWLPG  PM91751
       DSNIZLDL  PM91751

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM91751   DSNIDLOD DSNIFOD  DSNIWLPG DSNIZLDL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIDLOD
       DSNIFOD
       DSNIWLPG
       DSNIZLDL

      LISTEND
 UK98150 COVER LETTER END


 UK98223 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM97433 -
        ****************************************************************
        * USERS AFFECTED: All Distributed Data Facility (DDF) users.   *
        *                 Specifically those using LOBs or XML.        *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABND=04E-00D31010,                      *
        *                      LOC=DSNLILLM.DSNLCITR:0007              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        A DB2 for z/OS application executed a query to a remote server
        that returned a large amount of data but the application
        consumed only a part of it, leaving DB2 to maintain a control
        structure representing the request.
        The application then retrieves XML data from a remote server
        and this causes DB2 to incorrectly reinitialize the request
        correlator value even though a prior request is still pending.
        The application then executes another remote query but DB2
        assigned the same request correlator as the prior request.
        Since more than one active request was associated with the same
        correlator value, DB2 uses the wrong control structure to
1       process a subsequent SQL Fetch request and this causes the
        reported abend.

        DB2 requester LOB and XML processing has been changed to not
        reinitialize the request correlator if prior requests are still
        pending.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM97433
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNLCCLO  PM97433

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM97433   DSNLCCLO

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNLCCLO

      LISTEND
 UK98223 COVER LETTER END


 UK98262 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM95210 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS      *
        *                 users of remote stored procedures bound      *
        *                 with DESCSTAT(NO) which return result sets   *
        *                 with not null data types and have applied    *
        *                 PK23122/UK14047                              *
        ****************************************************************
        * PROBLEM DESCRIPTION: Error code -4228 issued by the IBM      *
        *                      Data Server Driver for JDBC when using  *
        *                      JDBC meta data stored procedures and    *
        *                      PM87510/UK94693 was previously applied. *
        *                                                              *
        *                      Incorrect SQLTYPE returned on remote    *
        *                      DESCRIBE cursor when                    *
        *                      PM87510/UK94693 was previously applied. *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        After applying PM87510/UK94693,
        remote stored procedures with static SQL bound, using
        the DESCSTAT=NO bind option or zparm, return nullable
        data types for all columns during DESCRIBE.
        Column type output in DESCRIBE processing is changed to return
        the correct nullability.

        Additional keywords: SQLDESCRIBE INCORROUT SQLSP DB2SP DB2DDF
1                            SQLSTOREDPROC
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM95210
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXEDC1  PM95210

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM95210   DSNXEDC1

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXEDC1

      LISTEND
 UK98262 COVER LETTER END


 UK98271 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM94123 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of RECOVER         *
        *                 utility.                                     *
        ****************************************************************
        * PROBLEM DESCRIPTION: (1) ABEND04E RC00C90101 IN DSNIUNDO     *
        *                      ERQUAL500B DURING RECOVER WITH BACKOUT  *
        *                      YES (2) RECOVER TABLESPACE using Flash  *
        *                      copy w/consistency for UTS table space  *
        *                      may not back out all the rows for       *
        *                      uncommitted transactions.               *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        (1) During LOGUNDO phase of RECOVER BACKOUT YES may results
        incorrectly perform sanity check for partition number for the
        segmented table spaces which results in Abend04E RC00C90101
        ERQUAL500B in DSNIUNDO. (2) During LOGCSR phase of RECOVER
        from flash copy data set, for segmented table space, table
        OBID was incorrectly used as a partition number which resulted
        in skipping log records for the segmented table space during
        LOGUNDO phase of RECOVER utility.
          The logic is changed to correctly derive the partition
        number from the UR summary checkpoint log record for each
        segmented, partition and UTS table spaces.
        The logic is modified to calculate the correct partition number
        to avoid data loss during RECOVERing page set using flash copy
        or RECOVER utility with BACKOUT YES option.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM94123
    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
       DSNIRCSR  PM94123

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM94123   DSNIRCSR

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNIRCSR

      LISTEND
 UK98271 COVER LETTER END


 UK98290 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM94229 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 10 for z/OS ODBC/CLI        *
        *                 running with LIMITEDBLOCKFETCH=1.            *
        ****************************************************************
        * PROBLEM DESCRIPTION: Following a successful fetch of         *
        *                      a partial rowset, the number of rows    *
        *                      returned in the pcrow argument          *
        *                      of SQLExtendedFetch() is always         *
        *                      one more than the number of rows        *
        *                      that were actually fetched.             *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Following a successful fetch of a partial rowset, the number
        of rows that were actually fetched is returned either in the
        pcrow argument of SQLExtendedFetch() or in the
        SQL_ATTR_ROWS_FETCHED_PTR statement attribute after each
        call to SQLFetchScroll().  With LIMITEDBLOCKFETCH=1, the row
        count returned is always one more than the actual number
        of rows that were fetched.
        Code has been updated to return the correct row count when
        fetching a partial rowset with LIMITEDBLOCKFETCH=1.
    COMPONENT:  5740-XYR02-JDBAA17
    APARS FIXED: PM94229
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR02 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNAOC27  PM94229
       DSNAOG02  PM94229
       DSNAOG04  PM94229
       DSNAOG08  PM94229
       DSNAOG27  PM94229
       DSNAOCLI  PM94229
       DSNAOSDK  PM94229
1
      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM94229   DSNAOC27 DSNAOG02 DSNAOG04 DSNAOG08 DSNAOG27 DSNAOCLI
                 DSNAOSDK

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNAOC27
       DSNAOG02
       DSNAOG04
       DSNAOG08
       DSNAOG27
       DSNAOCLI

      MACROS
       DSNAOSDK

      LISTEND
 UK98290 COVER LETTER END


 UK98291 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM94513 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 10 and 11 for z/OS who use  *
        *                 IBM DB2 Analytics Accelerator.               *
        ****************************************************************
        * PROBLEM DESCRIPTION: Incorrect results may be returned       *
        *                      when a query with OLAP function AVG is  *
        *                      used.                                   *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Incorrect results may be returned when a query with OLAP
        function AVG is offloaded to the accelerator and the AVG
        argument is a decimal, integer, smallint, or bigint.

        Keywords:
        IDAAV3R1/K SQLOLAP SQLAVG SQLINCORR SQLINCORROUT INCORROUT
        DB2INCORR/K SQLAVG
        Code is fixed to return the correct results.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM94513
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXONZS  PM94513

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM94513   DSNXONZS

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:
1
      MODULES
       DSNXONZS

      LISTEND
 UK98291 COVER LETTER END


 UK98355 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM95147 -
        ****************************************************************
        * USERS AFFECTED: ALL DB2 10 for z/OS and DB2 11 for z/OS      *
        *                 users of LOAD with ENFORCE CONSTRAINTS.      *
        ****************************************************************
        * PROBLEM DESCRIPTION: LOAD of child table with ENFORCE        *
        *                      CONSTRAINTS with a foreign key          *
        *                      defined on a VARCHAR column resulted    *
        *                      in MSGDSNU399I reporting errors for     *
        *                      valid column values.                    *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available.         *
        ****************************************************************
        Customer ran a LOAD utility for a child table which had
        two foreign keys defined for columns which also had
        varying length indexes defined on these same columns.

        When processing the foreign keys, the varying length
        attribute was not handled properly for the second
        foreign key, thus resulting in MSGDSNU399I and an
        error report of multiple referential integrity (RI)
        violations where there should have been no errors.

        Because of the RI errors, the DISCARD limit was reached
        thus failing the LOAD utility with MSGDSNU317I.

        Upon restart, of the failed utility, ABEND04E RC00C90101
        in DSNICMT2 ERQUAL500D was encountered.

        Additional keywords: DB2OVRLAY/M DB2OVRLAY/N SMCOVERLAY
        Code has been changed to handle foreign key processing
        for RI constraints on the same columns as an index
        so that, for multiple FKs, all constraints subsequent to the
        first are processed independently from the underlying index.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM95147
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNURWIK  PM95147

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM95147   DSNURWIK

1     THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNURWIK

      LISTEND
 UK98355 COVER LETTER END


 UK98357 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM95688 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 and 11 for z/OS users of XML      *
        *                 publishing function.                         *
        ****************************************************************
        * PROBLEM DESCRIPTION: The microseconds part in TIMESTAMP is   *
        *                      truncated when:                         *
        *                      1. A package is bound on DB2 9 and the  *
        *                         package contains XML publishing      *
        *                         function that has the TIMESTAMP      *
        *                         value as an input argument.          *
        *                      2. Running the package on DB2 10.       *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The microseconds part in TIMESTAMP is truncated when:
        1. A package is bound on DB2 9 and the package contains XML
           publishing function that has the TIMESTAMP value as an
           input argument.
        2. Running the package on DB2 10.

        For example:
          The CREATE TABLE statement below will create a table with
          a TIMESTAMP column.

            CREATE TABLE T1
            (
              TTIME  TIMESTAMP
            );

          The following query contains XML publishing function with the
          TIMESTAMP column TTIME as the input argument.

            SELECT XML2CLOB (
                     XMLELEMENT(NAME "C", T1.TTIME)
                   ) INTO :HV
            FROM T1;

          When this query is bound into a package on DB2 9 and runs on
          DB2 10, the microseconds part in the TTIME is truncated and
          the query returns the incorrect result as below:
            <C>2013-08-23T15:03:54</C>

          instead, the correct result should be:
            <C>2013-08-23T15:03:54.965551</C>
1       DB2 is modified so the correct result will be returned.

        Additional Keyword: SQLXML SQLINCORR INCORROUT SQLINCORROUT
                            DB2INCORR/K XMLALL XMLINCORR
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM95688
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXRPUF  PM95688

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM95688   DSNXRPUF

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXRPUF

      LISTEND
 UK98357 COVER LETTER END


 UK98463 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM96103 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users of the ENFM        *
        *                 process.                                     *
        ****************************************************************
        * PROBLEM DESCRIPTION: When running DSNTIJEN on one member     *
        *                      of a DS group other members received    *
        *                      abends until they were stopped          *
        *                      and started.                            *
        *                      ABEND04E in DSNB1PER+0B7A RC00C202AA    *
        *                      ABEND04E in DSNIIMSI:5006 RC00C90101    *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Running DSNTIJEN on one member and a workload on other members
        received abends. After DSNTIJEN finished and the other members
        were stopped and started the applications ran successfully.
        DB2 has been updated to serialize the workload
        on other members with the member that is running the DSNTIJEN
        JOB.

        ADDITIONAL KEYWORDS DB2MIGV10/K
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM96103
    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      DSNGEFLC  PM96103
       DSNGEPDL  PM96103
       DSNGEPIS  PM96103
       DSNGEPLC  PM96103

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM96103   DSNGEFLC DSNGEPDL DSNGEPIS DSNGEPLC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNGEFLC
       DSNGEPDL
       DSNGEPIS
       DSNGEPLC

      LISTEND
 UK98463 COVER LETTER END


 UK98497 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM97729 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS      *
        *                 utility users of UNLOAD with SPANNED YES     *
        ****************************************************************
        * PROBLEM DESCRIPTION: UNLOAD SPANNED YES allocates the        *
        *                      VBS SYSREC data set with an LRECL       *
        *                      which is not 32768.                     *
        *                                                              *
        *                      No error was issued when SYSREC was     *
        *                      directed to SYSOUT for UNLOAD SPANNED   *
        *                      YES.                                    *
        ****************************************************************
        * RECOMMENDATION: Apply corrective PTF when available          *
        ****************************************************************
        UNLOAD SPANNED YES allocated a VBS data set with LRECL=32756
        even though logical records in the data set were greater than
        32K (32K = 32768).  IDCAMS PRINT of the data set ended with
        S002-0004.

        IDCAMS does not support VBS data sets with logical records
        greater than 32760 and should issue IDC0005I.


        No error was issued when SYSREC was directed to SYSOUT for
        UNLOAD SPANNED YES.  This combination is not allowed.
        UNLOAD SPANNED YES uses a VBS data set for SYSREC to allow for
        records longer than 32K.  VBS data sets which have logical
        records longer than 32K should have LRECL=32768.  If LRECL is
        less than 32768 all records must be less than 32K or errors
        might occur.  UNLOAD and LOAD using SPANNED YES is intended
        for logical records greater than 32K; setting LRECL=32768 is
        appropriate in this case.

1
        Issue DSNU034I and abend with reason code '00E40070'x when
        SYSREC is directed to SYSOUT for UNLOAD SPANNED YES.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM97729
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DOCUMENTATION:
        PM58206 introduces the following changes to externals:

          Changed option for utility TEMPLATE:
          NBRSECND integer
          Specifies the division of secondary space allocations. After
          the primary space is allocated, an amount of space equal to
          the estimated required space is divided into the specified
        | number of secondary allocations.  Individual utilities may
        | request larger secondary extents to compensate for localized
        | uncertainty in the space estimations.  The integer value must
          be in the range from 1 to 10.
          The default value is 10.

          Changed text for utility TEMPLATE:
          Extent allocation for disk data sets
          By default, for data sets on disk, 100 percent of the required
          space that is estimated by DB2 is allocated as a primary
          quantity. If this amount of space is typically not available
          on a single volume, specify the PCTPRIME option with a value
          lower than 100. Alternatively, if you want the upper limit of
          the primary quantity based on size instead of percentage, use
          the MAXPRIME option.
          After the primary space is allocated, a secondary quantity
          that is equal to the estimated required space is divided into
        | the specified number of secondary extents.  Individual
        | utilities may request larger secondary extents to compensate
        | for localized uncertainty in the space estimations. This
          number is identified by the NBRSECND option. If you specify
          either PCTPRIME or MAXPRIME, any secondary allocation requests
          are limited to the size of the primary allocation.
      ACTION:
        ***Action for PM97729:

        See PM97729 APAR/PTF text for additional information.

        PM97729 corrects the following problem:
        SYSOUT should not be specified on the SYSREC DD for
        UNLOAD SPANNED YES.  In some cases, no error occured.
        With PM97729, DSNU034I with reason code X'00E40070'
        will be issued.
      ACTION:
        ***Action for PM91942:

        See PM91942 APAR/PTF text for additional information.

        PM91942 corrects the following problem:

1         UNLOAD SPANNED YES allocated a VBS data set with LRECL=32756
          even though logical records in the data set were greater than
          32K (32K = 32768).  IDCAMS PRINT of the data set ended with
          S002-0004 because a logical record length was greater than
          LRECL for the data set.

        UNLOAD SPANNED YES will be corrected to use LRECL 32768 for VBS
        data sets to allow for logical records greater than 32K.
        Existing IDCAMS does not support VBS data sets with logical
        records greater than 32760 so this fix could cause IDCAMS to
        issue IDC0005I in this case.

        Prior to PM91942, if UNLOAD SPANNED YES generated a SYSREC with
        all logical records less than 32760, IDCAMS against that SYSREC
        would not issue IDC0005I; however, this SYSREC would not be
        correct for appending logical records greater than 32K on a
        subsequent UNLOAD.

        If it is known that all logical records generated by UNLOAD
        are less than 32K, specifying SPANNED NO or omitting SPANNED
        may be used to generate a format VB data set; otherwise,
        UNLOAD SPANNED YES (causing a VBS data set with LRECL=32768)
        is appropriate.
      ACTION:
        The PTF for APAR PM88695 has modified CSECTs in both the
        DSNUT101 and DSNUTILA unload modules, affecting the utility
        batch and DB2 DBM1 address spaces. After the PTF has been
        applied, it will become active in the utility batch address
        space immediately upon job submission, while it will not take
        effect in the DB2 DBM1 address space until DB2 is stopped and
        started.

        The PTF does not have to be applied to all members in a data
        sharing environment simultaneously, and may be staged across
        each member.  However, until the fix is active in both the
        utility batch and DB2 DBM1 address spaces, the problem the
        PTF addresses will not be resolved.
      ACTION:
        *** Action for PM58206 ***
        The UNLOAD utility estimates the space requirement for the
        SYSREC data set based on the statistics from catalog
        tables.
        A RUNSTATS against the target table space is recommended
        prior to the UNLOAD to ensure the accurate estimation
        for space requirement.
    COMMENTS:
        The PTF for APAR PM87978 adds the keywords STRIP TRAILING to
        the generated SYSPUNCH output data set for columns defined as
        CHAR MIXED when data is unloaded from an EBCDIC table to UNICODE
        output.  For example:
 ¬
                COL1  CHAR(100) MIXED STRIP TRAILING
        The PTF for apar PM79586 adds the keywords STRIP TRAILING to
        the generated SYSPUNCH output data set for columns defined as
        CHAR MIXED when data is unloaded from a UNICODE table to EBCDIC
        output.  For example:
1¬
                COL1  CHAR(100) MIXED STRIP TRAILING
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUGSDA  PM97729
       DSNUULDB  PM97729
       DSNUULPB  PM97729

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM97729   DSNUGSDA DSNUULDB DSNUULPB

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUGSDA
       DSNUULDB
       DSNUULGL
       DSNUULIA
       DSNUULPB
       DSNUULXA
       DSNUUNLD

      LISTEND
 UK98497 COVER LETTER END


 UK98505 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM95478 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS users.                   *
        ****************************************************************
        * PROBLEM DESCRIPTION: Preconditioning support for new         *
        *                      function.                               *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        This APAR, PM95478, is a preconditioning APAR for PM95731.
        This APAR, PM95478, is a preconditioning APAR for PM95731.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM95478
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNFMDIR  PM95478
       DSNFUDRE  PM95478
       DSNGDART  PM95478
       DSNUBACI  PM95478
       DSNUBAII  PM95478
       DSNUBAI2  PM95478
       DSNUCAIN  PM95478
       DSNUCBRL  PM95478
       DSNUCBRS  PM95478
       DSNUCBVR  PM95478
       DSNUCINT  PM95478
1      DSNUGDTC  PM95478
       DSNUGSRX  PM95478
       DSNUKINP  PM95478
       DSNUKINT  PM95478
       DSNUMDEL  PM95478
       DSNUMSGE  PM95478
       DSNUMSTA  PM95478
       DSNUQUIA  PM95478
       DSNURBUS  PM95478
       DSNURUSO  PM95478
       DSNUSSRI  PM95478
       DSNUULIA  PM95478
       DSNUYAS1  PM95478
       DSNU2AII  PM95478
       DSN9SCNA  PM95478

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM95478   DSNFMDIR DSNFUDRE DSNGDART DSNUBACI DSNUBAII DSNUBAI2
                 DSNUCAIN DSNUCBRL DSNUCBRS DSNUCBVR DSNUCINT DSNUGDTC
                 DSNUGSRX DSNUKINP DSNUKINT DSNUMDEL DSNUMSGE DSNUMSTA
                 DSNUQUIA DSNURBUS DSNURUSO DSNUSSRI DSNUULIA DSNUYAS1
                 DSNU2AII DSN9SCNA

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNFMDIR
       DSNFUDRE
       DSNGDART
       DSNUBACI
       DSNUBAII
       DSNUBAI2
       DSNUCAIN
       DSNUCBRL
       DSNUCBRS
       DSNUCBVR
       DSNUCINT
       DSNUGDTC
       DSNUGSRX
       DSNUKINP
       DSNUKINT
       DSNUMDEL
       DSNUMSGE
       DSNUMSTA
       DSNUQUIA
       DSNURBUS
       DSNURUSO
       DSNUSSRI
       DSNUULIA
       DSNUYAS1
       DSNU2AII
       DSN9SCNA

      LISTEND
 UK98505 COVER LETTER END

1
 UK98533 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM98360 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 for zOS.                    *
        ****************************************************************
        * PROBLEM DESCRIPTION: A -SET LOG RESUME command may hang      *
        *                      when logging has been suspended by      *
        *                      the -SET LOG SUSPEND command.           *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        A -SET LOG RESUME command can hang during command
        authorization checking when logging has been suspended
        by the -SET LOG SUSPEND command.  Cascading contention
        from the -SET LOG SUSPEND command can cause the command
        authorization service task to hang until logging is resumed.
        DSN9SCNP has been changed to account for new -SET LOG command
        keywords when attempting to avoid command authorization
        contention processing the -SET LOG RESUME command.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM98360
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSN9SCNP  PM98360

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM98360   DSN9SCNP

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSN9SCNP

      LISTEND
 UK98533 COVER LETTER END


 UK98543 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM94543 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS version 10 and DB2 for      *
        *                 z/OS version 11 users of SQL statements      *
        *                 with range list access and boolean term      *
        *                 predicate is not applied as matching         *
        *                 predicate in all OR legs.                    *
        ****************************************************************
        * PROBLEM DESCRIPTION: Incorrect output may be returned when   *
        *                      query satisfies all of the following    *
        *                      conditions:                             *
        *                      1 Range list access path is chosen      *
1       *                      2 Boolean term predicate is not applied *
        *                        as matching predicate in all OR legs. *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        Incorrect output may be returned when query satisfies all the
        following conditions:
        1 Range list access path is chosen.
        2 Boolean term predicate is not applied as matching predicate
          in all OR legs.

        An example for incorrect output is shown below:
        CREATE TABLE T(C1 INT,C2 INT,C3 INT,C4 INT,C5 INT);
        CREATE INDEX IDX1 ON T(C1,C2,C3,C4);
        SELECT COUNT(*)
        FROM T
        WHERE C1=? AND C3=? AND
              (C2>? OR(C2=? AND C3>?) OR (C2=? AND C3<?));
        SOLUTION:
        DB2 has been modified to correctly process the aforementioned
        SQL statement,so there will be no incorrect output.

        Additional Keywords: SQLINCORR SQLINCORROUT DB2INCORR/K
                             SQLRANGELIST SQLOR
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM94543
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        PM94543 corrects a problem of incorrect output
        returned when a range list access path is chosen
        for the table and the boolean term predicate not
        applied as matching predicate in all OR legs.
      DB2BIND:
        ***Action for PM85238:

        See PM85238 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM85238 corrects a problem of incorrect output may be
        returned when a range list access path is chosen for the
        table and one of non-boolean term predicates under OR is not
        the matching predicate.


        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
      DB2BIND:
        ***Action for PM57955:

        See PM57955 APAR/PTF text for additional information about
        why a REBIND is necessary.

1       PM57955 corrects a problem of ABEND04E RC00E70005 in DSNXORGL
        P130 when query with range list access (ACCESSTYPE = 'NR' in
        PLAN_TABLE) participated in parallel sort-merge join group.

        To make this fix effective for a static application, it must be
        rebound after application of this PTF.  Review the PTF cover
        letter to determine which, if any, applications could be
        affected by this change.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXORGL  PM94543

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM94543   DSNXORGL

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXORGL

      LISTEND
 UK98543 COVER LETTER END


 UK98545 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM95356 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 and DB2 11 for z/OS users         *
        *                 who use audit policies.                      *
        *                                                              *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00E70005 CSECT DSNXAMAP      *
        *                      occurred when more than 32 audit        *
        *                      policies were started. This led to      *
        *                      starting of incorrect traces and        *
        *                      storage overlay.                        *
        *                                                              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        ABEND04E RC00E70005 CSECT DSNXAMAP occurred when more than
        32 audit policies were incorrectly started. This did not set
        error return code. The abend in the audit policy processing
        was re-tried. Due to an uninitialized variable and successful
        return code, incorrect traces were started and also led to
        storage overlay.

        Code has been changed to return error with new reason code
        '00E70031'X instead of abend, if more than 32 audit policies
        are started.

    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM95356
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
1                LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DOCUMENTATION:
        00E70031

        Explanation
        The maximum number of audit policies exceeded in the subsystem.
        No more than 32 audit policies can be started in a subsystem.

        System action
        The audit policy is not started. This reason code is in the
        IFCID 0362 trace record.

        System programmer response
        Issue the following command to identify the audit policies
        that are started: DISPLAY TRACE(AUDIT) DETAIL(2)
        Then, issue a STOP TRACE command to stop an audit policy
        before starting one.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNWVCST  PM95356
       DSNXAMAP  PM95356

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM95356   DSNWVCST DSNXAMAP

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNWVCST
       DSNXAMAP

      LISTEND
 UK98545 COVER LETTER END


 UK98551 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM97664 -
        ****************************************************************
        * USERS AFFECTED: All users of DB2 for z/OS that may encounter *
        *                 soft cancel failures like RC00E50013 during  *
        *                 backout activity which involves updates to   *
        *                 table space space map page.                  *
        ****************************************************************
        * PROBLEM DESCRIPTION: ESTAE ENTERED IRLM ABEND U2027 MODULE   *
        *                      DXRRL150+0B8C                           *
        *                      DB2 S004F ABENDS                        *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        During log record backout processing, space map pages get
        updated to reflect activity on data pages. A soft cancel
        failure RC00E50013 was encountered during this backout and
        the cancel forced critical exit routines to be driven.

        The critical exit routines correctly bypassed any retry logic
1       for soft cancel failures since 00E50013 is not a retryable
        failure. The routines released space map pages and any latch
        that was held but there was a window in which an IRLM control
        block representing P-lock was freed prematurely. This premature
        freeing led to a reuse of the block and subsequent IRLM and DB2
        failures.
        DB2 code has been changed to avoid releasing the page and the
        latch on the page in the critical program recovery logic for
        soft cancel RC00E50013 failures during space map undo activity.
        Any necessary page cleanup activity will now default to the
        recovery manager logic.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM97664
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNILSMG  PM97664
       DSNILSMU  PM97664

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM97664   DSNILSMG DSNILSMU

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNILSMG
       DSNILSMU

      LISTEND
 UK98551 COVER LETTER END


 UK98569 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM94086 -
        ****************************************************************
        * USERS AFFECTED: All DB2 V9, 10 or 11 for z/OS users of an    *
        *                 UPDATE statement that contains a row         *
        *                 expression assignment and a scalar full      *
        *                 select returning empty is assigning to a NOT *
        *                 NULL column in the the row expression        *
        *                 assignment.                                  *
        ****************************************************************
        * PROBLEM DESCRIPTION: Incorrect output or ABEND0C7 RC00000000 *
        *                      at the location DSNXGRDS DSNXROHB       *
        *                      OFFSET273C for V9(OFFSET27B8 for V10,   *
        *                      OFFSET2550 for V11) could be caused by  *
        *                      an UPDATE statement that contains a row *
        *                      expression assignment and a scalar full *
        *                      select returning empty is assigning to  *
        *                      a NOT NULL column in the the row        *
        *                      expression assignment.                  *
        ****************************************************************
        * RECOMMENDATION:                                              *
1       ****************************************************************
        An example is shown below:

        CREATE TABLE T1(
         C1 DECIMAL(15,2) NOT NULL,
         C2 CHAR(4)
        );

        INSERT INTO T1 VALUES(1111, 'C201');

        UPDATE T1
        SET (T1.C1, T1.C2)
          = ((SELECT 0 FROM SYSIBM.SYSDUMMY1 WHERE 1=9)
              , 'C202')
        WHERE T1.C2 = 'C201';

        SELECT * FROM T1;

        The UPDATE statement should return an SQLCODE -407, while it
        doesn't. So the column T1.C1 is updated incorrectly, then the
        SELECT statement may cause the ABENDs or return invalid data for
        the column T1.C1.

        DB2 did not correctly process the aforementioned SQL statements,
        which caused the ABEND or incorrect output.
        DB2 has been modified to correctly process the aforementioned
        SQL statements, so SQLCODE -407 will be issued for the UPDATE
        statement, and there will be no ABEND or incorrect output.

        Additional keywords: SQLUPDATE SQLSCALAR SQLFULLSELECT
                             SQLSCALARFULSEL SQLNOTNULL SQLCODE407
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM94086
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
      DB2BIND:
        ***Action for PM94086:

        See PM94086 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM94086 corrects a problem that incorrect output or ABEND0C7
        RC00000000 at the location DSNXGRDS DSNXROHB OFFSET273C for
        V9(OFFSET27B8 for V10, OFFSET2550 for V11) could be caused by an
        UPDATE statement that contains a row expression assignment and a
        scalar full select returning empty is assigning to a NOT NULL
        column in the the row expression assignment.

        To make this fix effective for a static application, it must 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 PM74746:

1       See PM74746 APAR/PTF text for additional information about
        why a REBIND is necessary.

        PM74746 corrects a bind time problem that can result in an
        ABEND0C6-6 at location DSNXVCDF+27B or +27D for a query
        referencing a large complex view that has a UNION ALL and
        decimal arithmetic.

        To make this fix effective for a static application, it must 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:
        Please note that the following action will need to be performed
        along with applying the ptf for this apar.

        Any nested views that are created with the symptoms mentioned in
        the apar description will need to be dropped and recreated.
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXOP1   PM94086

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM94086   DSNXOP1

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXOP1

      LISTEND
 UK98569 COVER LETTER END


 UK98586 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM97275 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS users of multi-table simple *
        *                 table spaces who have run ALTER TABLE ADD    *
        *                 COLUMN prior to V8 and now run REORG utility *
        *                 in DB2 9 or higher releases, where the REORG *
        *                 changes row format from basic row format     *
        *                 (BRF) to reordered row format (RRF).         *
        ****************************************************************
        * PROBLEM DESCRIPTION: ABEND04E RC00E40316 DSNURSCN+32E4       *
        *                      during REORG UNLOAD phase.              *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        During REORG of a simple table space, the ABEND04E RC00E40316
        failure was encountered. There were multiple tables in the
        table space and columns were ALTER ADDed to the tables likely
        before DB2 V6. The reported abend occurred when migrating to DB2
        10 NFM but could also happen in other DB2 releases.

1       The tables contained short rows after ALTER ADD COLUMN and
        needed a REORG to expand out all rows. REORG UNLOAD was using
        an internal inline path for unload of the rows however the
        presence of short rows forced the code to take an out of line
        code path.

        Simple table spaces (non-partitioned, non-segmented) allow rows
        belonging to different tables to share the same data page. The
        abend occurred after a short row was encountered during BRF to
        RRF conversion and there was a switch in the unload scan from
        one table to another on the same data page.

        An internal control block that manages row positioning was not
        set correctly for the new table. After DSNIFNXR returned the
        internal reason 00C90002 to the utility code, the
        aforementioned DSNURSCN abend was issued.
        For the cases of short rows in simple table spaces with multiple
        tables, DB2 code has been changed to set row positioning
        information correctly.

        To resolve the issue, this APAR should be applied and REORG
        rerun.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM97275
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNUCRUL  PM97275
       DSNUKIUL  PM97275
       DSNURFBR  PM97275
       DSNURSCN  PM97275
       DSNUSTBL  PM97275
       DSNUULXA  PM97275

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM97275   DSNUCRUL DSNUKIUL DSNURFBR DSNURSCN DSNUSTBL DSNUULXA

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNUCRUL
       DSNUKIUL
       DSNURFBR
       DSNURSCN
       DSNUSTBL
       DSNUULXA

      LISTEND
 UK98586 COVER LETTER END


 UK98589 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM96597 -
1       ****************************************************************
        * USERS AFFECTED: All DB2 users of the PKGREL(BNDOPT) DDF      *
        *                 OPTION.                                      *
        ****************************************************************
        * PROBLEM DESCRIPTION: A dump with a title similar to          *
        *                                                              *
        *                      DUMP TITLE=DMP1,ABND=0C4-00000038,      *
        *                        U=FSN0APP ,M=N  ,C=101.LOCN=:         *
        *                        :FFFF:45.1.3.16   ,                   *
        *                         PSW=077C0001FE35DEDC,A=00C0          *
        *                                                              *
        *                      was received for a distributive         *
        *                      thread.                                 *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        ABEND0C1 and ABEND0C4 can be received when a DDF thread
        executes RELEASE(DEALLOCATE) packages under the PKGREL(BNDOPT)
        DDF option. The wrong lock can be acquired for the package
        and storage can be freed while it is still in use. The
        abends can occur if the freed storage is referenced.
        The code has been updated to insure that the correct duration
        is used for the lock.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM96597
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNGEFLC  PM96597
       DSNGEPLC  PM96597

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM96597   DSNGEFLC DSNGEPLC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNGEFLC
       DSNGEPLC

      LISTEND
 UK98589 COVER LETTER END


 UK98618 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM95121 -
        ****************************************************************
        * USERS AFFECTED: All DB2 9 for z/OS, DB2 10 for z/OS, and     *
        *                 DB2 11 for z/OS users of a pair-wise join    *
        *                 query.                                       *
        ****************************************************************
        * PROBLEM DESCRIPTION: An incorrect out may occur when a       *
        *                      pair-wise join query cannot use         *
1       *                      sparse index due to some limitation.    *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An incorrect out may occur when a pair-wise join query cannot
        use a sparse index due to some limitation. In such situations,
        the pair-wise join query setting needs to be dynamically
        adjusted to handle a non-sparse index method.

        Following is an example of such failing query:
        SELECT *
          FROM TF, TA, TB, TC
         WHERE TF.C1 = TA.C1
           AND TF.C1 = TB.C2
           AND TF.C3 = TC.C3
        ;

        Note: In this example, the dimension table is (TA + TB) and
              the sum of the two table columns length + sort key length
              is greater than 4K size.
        DB2 is modified to dynamically adjust the pair-wise join setting
        if the non-sparse index scenario occurs.

        Additional Keywords: SQLPAIRWISEJOIN SQLINCORR INCORROUT
                             SQLINCORROUT DB2INCORR/K SQLSPARSEINDEX
                             SPARSEINDEX
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM95121
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXRPJP  PM95121

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM95121   DSNXRPJP

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXRPJP

      LISTEND
 UK98618 COVER LETTER END


 UK98635 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM93879 -
        ****************************************************************
        * USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS      *
        *                 users of ALTER LOB-COLUMN.                   *
        ****************************************************************
        * PROBLEM DESCRIPTION: An incorrect output of catalog table    *
        *                      SYSIBM.SYSCOLUMNS column LENGTH2 value  *
1       *                      may occur when altering a LOB column's  *
        *                      maximum length for a table in a non-    *
        *                      partitioned segmented tablespace.       *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        An incorrect output of catalog table SYSIBM.SYSCOLUMNS column
        LENGTH2 may occur when altering a LOB column maximum length for
        a table in a non-partitioned segmented tablespace. It is because
        when altering a LOB column maximum length for a table in a non-
        partitioned segmented tablespace, DB2 does not properly update
        the corresponding LOB auxiliary table's column length in the
        catalog SYSIBM.SYSCOLUMNS field LENGTH2.

        Following is an example of such failing scenario:
        SET CURRENT RULES = 'STD';
        DROP DATABASE MYDB;
        RETCODE = SQLCHECK(0,-551);
        COMMIT;

        CREATE DATABASE MYDB CCSID UNICODE;
        CREATE TABLESPACE MYTS SEGSIZE 4  IN MYDB CCSID UNICODE;

        CREATE TABLE MYTB(ROW_ID ROWID NOT NULL GENERATED ALWAYS,
                          COLLOB CLOB(10)
                         ) IN MYDB.MYTS;

        SELECT TBNAME, LENGTH, LENGTH2
          FROM SYSIBM.SYSCOLUMNS
         WHERE TBNAME LIKE 'MYTB%';

        ALTER TABLE MYTB ALTER COLLOB SET DATA TYPE CLOB(2000);

        SELECT TBNAME, LENGTH, LENGTH2
          FROM SYSIBM.SYSCOLUMNS
         WHERE TBNAME LIKE 'MYTB%';

        DB2 is modified to properly update the catalog table SYSIBM.
        SYSCOLUMNS column LENGTH2 field when altering a LOB column's
        maximum length.

        One way to find out if the LOB column's maximum length in both
        base table and the corresponding auxiliary table are the same or
        not is running a REPAIR DBD job with DIAGNOSE option. For
        example:
          REPAIR DBD DIAGNOSE DATABASE   MYDB

        If the maximum length of a LOB column in base table and the
        auxiliary table are different, the REPAIR job will report an
        error. Following is an example of the error message:

        DSNU920I    DSNUEDRT -   OBDS DIFFER AT OFFSET X'000000AA'
                                 OBDRAFLL(3)
        DSNU904I    DSNUEDRT -     EXISTING VALUE  X'000007D0'
        DSNU905I    DSNUEDRT -     REBUILT  VALUE  X'0000000A'
        DSNU913I    DSNUEDDR - OBD X'0008' COMPARISON COMPLETE --
1                              1 ERRORS WERE FOUND


        Additional Keywords: SQLALTER SQLLOB SQLINCORR INCORROUT
                             SQLINCORROUT
                             NON-UTS SEGMENT TABLESPACE
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM93879
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNXIALC  PM93879

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM93879   DSNXIALC

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNXIALC

      LISTEND
 UK98635 COVER LETTER END


 UK98675 COVER LETTER START
    PROBLEM DESCRIPTION(S):
      PM92628 -
        ****************************************************************
        * USERS AFFECTED: All DB2 for z/OS users with applications     *
        *                 that utilize Declared Global Temporary       *
        *                 Tables and the TRUNCATE statement with       *
        *                 the REUSE option.                            *
        ****************************************************************
        * PROBLEM DESCRIPTION: An application can abend with           *
        *                      ABEND04E RC00C90101 DSNIBHUN ERQUAL5016 *
        *                      when a TRUNCATE statement               *
        *                      with REUSE option is rolled back.       *
        *                                                              *
        *                      A diagnostic dump with title            *
        *                      ABEND04E RC00C90101 DSNISGAU ERQUAL5123 *
        *                      can occur when a TRUNCATE statement     *
        *                      with REUSE option is executed and       *
        *                      the application deallocates.            *
        ****************************************************************
        * RECOMMENDATION:                                              *
        ****************************************************************
        The ABEND04E RC00C90101 DSNIBHUN ERQUAL5016 abend is caused
        by incorrectly setting the space class setting in segments
        greater than 1 during a mass delete triggered by the TRUNCATE
        with the REUSE option.  Setting the space class incorrectly
        allowed the space to be allocated as the application progresses.
        The changes cannot be completely undone during normal ROLLBACK
        or ROLLBACK caused by abort, thus the abend.
1
        The ABEND04E RC00C90101 DSNISGAU ERQUAL5123 diagnostic dump
        can be produced when the number of segments deallocated
        becomes a negative value; this may indicate a DB2 code problem.
        However, in this case it was just incorrect accounting by DB2.
        During TRUNCATE with REUSE the segments remain on the segment
        chain, but they were being incorrectly counted as deallocations.
        During undo the deallocation count was further decremented
        and eventually became negative.

        The diagnostic dump may be produced regardless of whether the
        application aborts or rolls back.  The diagnostic dump does not
        cause the application to fail.


        Additional Keywords: SQLDGTT SQLTRUNCATE SQLDELETE SQLROLLBACK
        DB2 is modified to correctly set the space class settings during
        TRUNCATE with REUSE.

        DB2 is also modified to correctly count the amount of data that
        is allocated and deallocated for Declared Global Temporary
        Tables.
    COMPONENT:  5740-XYR00-HDBAA10
    APARS FIXED: PM92628
    SPECIAL CONDITIONS:
      COPYRIGHT: 5740-XYR00 COPYRIGHT IBM CORP. 1982 2010
                 LICENSED MATERIAL - PROGRAM PROPERTY OF IBM
    COMMENTS:
      CROSS REFERENCE-MODULE/MACRO NAMES TO APARS
       DSNISEGD  PM92628

      CROSS REFERENCE-APARS TO MODULE/MACRO NAMES
       PM92628   DSNISEGD

      THE FOLLOWING MODULES AND/OR MACROS ARE AFFECTED BY THIS PTF:

      MODULES
       DSNISEGD

      LISTEND
 UK98675 COVER LETTER END

 READY
 END
User Communications
