IBM Support

PM83190: UNABLE TO EXCLUDE BASE/CLONE TABLES FROM FILTERS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Message ALAA506E indicating that base/clone tables are not
    supported can be generated even when the base/clone table is
    explicitly excluded. If base/clone pairs are present as EXCLUDE
    type filters (and they must be because base/clone pairs are not
    supported by Log Analysis Tool), the filters are still flagged
    as being in error. For example, if you have 2 tables:
    USER1.TABLE1
    USER1.TABLE2  (this table has a clone).
    and your filters are:
    Include USER1.TAB%
    Exclude USER1.TABLE2
    Log Analysis Tool still generates message ALAA506E indicating
    base/clone tables are not supported.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Log Analysis Tool.              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Message ALAA506E indicating that        *
    *                      base/clone tables are not supported     *
    *                      can be generated even when the          *
    *                      base/clone table is explicitly          *
    *                      excluded. If base/clone pairs are       *
    *                      present as EXCLUDE type filters (and    *
    *                      they must be because base/clone pairs   *
    *                      are not supported by Log Analysis       *
    *                      Tool), the filters are still flagged    *
    *                      as being in error. For example, if you  *
    *                      have 2 tables:                          *
    *                      USER1.TABLE1                            *
    *                      USER1.TABLE2  (this table has a clone). *
    *                      and your filters are:                   *
    *                      Include USER1.TAB%                      *
    *                      Exclude USER1.TABLE2                    *
    *                      Log Analysis Tool still generates       *
    *                      message ALAA506E indicating base/clone  *
    *                      tables are not supported.               *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM83190

  • Reported component name

    DB2 LOG ANALYSI

  • Reported component ID

    5655E6601

  • Reported release

    330

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-02-19

  • Closed date

    2013-04-04

  • Last modified date

    2013-05-06

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

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

    UK93151 UK93152

Modules/Macros

  • ALAGEN1  ALAGFLT  ALALF1
    

Fix information

  • Fixed component name

    DB2 LOG ANALYSI

  • Fixed component ID

    5655E6601

Applicable component levels

  • R320 PSY UK93151

       UP13/04/13 P F304

  • R330 PSY UK93152

       UP13/04/13 P F304

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":"3.3.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
06 May 2013