IBM Support

PQ90502: POSSIBLE BAD OUTPUT WHEN FILTERING ON SPECIFIC TYPES OF DML ACTIVITY ALAA172E

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When filtering on only UPDATEs, it is possible the results in
    the detail report will be be bad because INSERTs and DELETEs
    that occurred during the general report timeframe are excluded
    from the extract file (EXTFILE DD). These records, though not
    desired in this case for reporting purposes, must be included
    in the extract file for full row materialization purposes
    **************
    KEYWORDS
    ALAA172E-SQL stmt not valid due to: WHERE clause could not be
    generated.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Log Analysis.                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: When filtering on only UPDATEs, it is   *
    *                      possible the results in the detail      *
    *                      report will be be bad because INSERTs   *
    *                      and DELETEs that occurred during the    *
    *                      general report timeframe are excluded   *
    *                      from the extract file (EXTFILE DD).     *
    *                      These records, though not desired in    *
    *                      this case for reporting purposes, must  *
    *                      be included in the extract file for     *
    *                      full row materialization purposes       *
    *                      KEYWORDS                                *
    *                      ALAA172E-SQL stmt not valid due to:     *
    *                      WHERE clause could not be               *
    *                      generated.                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PQ90502

  • Reported component name

    DB2 LOG ANALYSI

  • Reported component ID

    5655E6601

  • Reported release

    210

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2004-06-22

  • Closed date

    2004-07-14

  • Last modified date

    2004-08-04

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

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

Modules/Macros

  •    ALAA16
    

Fix information

  • Fixed component name

    DB2 LOG ANALYSI

  • Fixed component ID

    5655E6601

Applicable component levels

  • R210 PSY UQ90656

       UP04/07/20 P F407

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.

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"210"}]

Document Information

Modified date:
12 April 2021