IBM Support

PH20317: QUERY ACCELERATION NOT WORKING WHEN ELIGIBLE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • When going through a VT the SQL Engine by default sets "Current
    Query Acceleration" to "Enable with Failback" which allows Db2
    to determine if it goes to Db2 native table or Accelerated
    table.
    
    This can be changed with the setting of OPTBNOQA which can be
    set in any VTB Rule.  Currently it is shipped in the ***MDTBL
    rule.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: ALL USERS                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Query acceleration                      *
    *                      not working when eligible               *
    ****************************************************************
    * RECOMMENDATION: APPLY PTF                                    *
    ****************************************************************
    Query acceleration not working when eligible
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PH20317

  • Reported component name

    DATA VIRT MGR Z

  • Reported component ID

    5698DVM00

  • Reported release

    110

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function / Xsystem

  • Submitted date

    2019-12-13

  • Closed date

    2020-02-06

  • Last modified date

    2020-03-02

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

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

Modules/Macros

  • AVZCDSAL AVZCDSOP AVZCMTCL AVZCS1HD AVZCSQOP AVZCTVOP AVZICSFX
    AVZIMPDS AVZMCLUP AVZMDTBL AVZO319D AVZO319N AVZO31AD AVZO31AN
    AVZO31BD AVZO31BN AVZO31CD AVZO31CN AVZO31DD AVZO31DN AVZO649D
    AVZO649N AVZO64AD AVZO64AN AVZO64BD AVZO64BN AVZO64CD AVZO64CN
    AVZO64DD AVZO64DN AVZOACDA AVZOBRSQ AVZOBRTV AVZODF9D AVZODF9N
    AVZODFAD AVZODFAN AVZODFBD AVZODFBN AVZODFCD AVZODFCN AVZODFDD
    AVZODFDN AVZODT9N AVZODTAN AVZODTBN AVZODTCN AVZODTDN AVZOICSF
    AVZOINAS AVZOIO31 AVZOIOMG AVZOKY9D AVZOKY9N AVZOKYAD AVZOKYAN
    AVZOKYBD AVZOKYBN AVZOKYCD AVZOKYCN AVZOKYDD AVZOKYDN AVZOLI9D
    AVZOLI9N AVZOLIAD AVZOLIAN AVZOLIBD AVZOLIBN AVZOLICD AVZOLICN
    AVZOLIDD AVZOLIDN AVZOPMS  AVZOPPA  AVZORXST AVZOTBEV AVZOVSSE
    AVZOVSUP AVZPB    AVZSBMIG AVZSEFCK AVZSQ29D AVZSQ29N AVZSQ2AD
    AVZSQ2AN AVZSQ2BD AVZSQ2BN AVZSQ2CD AVZSQ2CN AVZSQ2DD AVZSQ2DN
    AVZSQL9D AVZSQL9N AVZSQLAD AVZSQLAN AVZSQLBD AVZSQLBN AVZSQLCD
    AVZSQLCN AVZSQLDD AVZSQLDN AVZWSCLP AVZWSMFL
    

Fix information

  • Fixed component name

    DATA VIRT MGR Z

  • Fixed component ID

    5698DVM00

Applicable component levels

  • R110 PSY UI67730

       UP20/02/08 P F002  

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.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"110","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
27 March 2020