IBM Support

PM71137: EXPLAININPUTSCHEMA SUPPORT FOR BIND QUERY

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as new function.

Error description

  • New function support to EXPLAININPUTSCHEMA for BIND QUERY
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All DB2 10 for z/OS users using BIND        *
    *                  QUERY command.                              *
    *                                                              *
    *                                                              *
    *                                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1.There is an existing usability issue  *
    *                      with BIND QUERY, which is related to    *
    *                      the design of using the same set of     *
    *                      tables for both EXPLAIN output and      *
    *                      BIND QUERY input.It causes confusion    *
    *                      because the EXPLAIN tables contain      *
    *                      many rows for many different            *
    *                      statements but only a small subset of   *
    *                      these rows are intended to be used as   *
    *                      input to BIND QUERY.Users must clear    *
    *                      out the rows that aren't intended to    *
    *                      be passed into BIND QUERY.              *
    *                                                              *
    *                      2.The BIND QUERY LOOKUP (YES) can not   *
    *                      support to identify rows for statement  *
    *                      level optimization parameters hints     *
    *                      and update the corresponding QUERYID    *
    *                      in DSN_USERQUERY_TABLE.                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Two requirements are addressed by this APAR:
    
    1.There is an existing usability issue with BIND QUERY, which
    is related to the design of using the same set of tables for
    both EXPLAIN output and BIND QUERY input.It causes confusion
    because the EXPLAIN tables contain many rows for many different
    statements but only a small subset of these rows are intended
    to be used as input to BIND QUERY.Users must clear out the rows
    that aren't intended to be passed into BIND QUERY.
    
    2.The BIND QUERY LOOKUP (YES) can not support to identify rows
    for statement level optimization parameters hints and update
    the corresponding QUERYID in DSN_USERQUERY_TABLE.
    

Problem conclusion

Temporary fix

Comments

  • Two new functions are provided by this APAR:
    
    1.A new option is added to the BIND QUERY command called
    EXPLAININPUTSCHEMA. This option is used to specify the schema
    name for the tables used as input to BIND QUERY. This allow
    users to use different tables for EXPLAIN output and BIND QUERY
    intput, where the user only copies the rows to be input to BIND
    QUERY from the EXPLAIN output tables.
    
    Syntax:
    >>-BIND QUERY-+-------------+-+----------------------------+-><
                  |       .NO-. | |                            |
                  'LOOKUP(+YES+)' 'EXPLAININPUTSCHEMA('schema')'
    
    2.The BIND QUERY LOOKUP (YES) is enhanced to identify rows
    for statement level optimization parameters hints and update
    the corresponding QUERYID in DSN_USERQUERY_TABLE.
    

APAR Information

  • APAR number

    PM71137

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function

  • Submitted date

    2012-08-17

  • Closed date

    2012-11-26

  • Last modified date

    2013-01-02

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UK83750

Modules/Macros

  •    DSNECP00 DSNECP08 DSNECP70 DSNTBAP  DSNXOBNQ
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK83750

       UP12/12/12 P F212

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.



Document information

More support for: DB2 for z/OS

Software version: A10

Reference #: PM71137

Modified date: 02 January 2013


Translate this page: