IBM Support

PI92839: EXCLUDED XML / LOB COLUMNS STILL REQUIRE TRACKING FOR LOADFILE /SQL GENERATION

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Currently when generating a LOADFILE or SQL for an object that
    contains XML or a LOB column, Log Analysis Tool requires the
    tracking of the XML / LOB data or an ALAA088W message is issued.
    If these XML and LOB columns are excluded from the LOADFILE and
    SQL generation, the product should not require XML / LOB data to
    be tracked. This APAR will create a code path to not require the
    tracking of XML and LOB data when the columns are excluded.
    However, if XML / LOB data is needed for one object for the
    LOADFILE / SQL generation, then it must be tracked for all
    objects in the filter set.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of ALA350                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Currently when generating a LOADFILE or *
    *                      SQL for an object that                  *
    *                      contains XML or a LOB column, Log Analy *
    *                      Tool requires the                       *
    *                      tracking of the XML / LOB data or an    *
    *                      ALAA088W message is issued.             *
    *                      If these XML and LOB columns are exclud *
    *                      from the LOADFILE and                   *
    *                      SQL generation, the product should not  *
    *                      require XML / LOB data to               *
    *                      be tracked. This APAR will create a cod *
    *                      path to not require the                 *
    *                      tracking of XML and LOB data when the   *
    *                      columns are excluded.                   *
    *                      However, if XML / LOB data is needed fo *
    *                      one object for the                      *
    *                      LOADFILE / SQL generation, then it must *
    *                      be tracked for all                      *
    *                      objects in the filter set.              *
    *                                                              *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION: Apply the PTF                                *
    ****************************************************************
    

Problem conclusion

  • Apply the PTF
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI92839

  • Reported component name

    DB2 LOG ANALYSI

  • Reported component ID

    5655E6601

  • Reported release

    350

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-01-23

  • Closed date

    2018-03-05

  • Last modified date

    2018-04-03

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

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

Modules/Macros

  • ALABSQL
    

Fix information

  • Fixed component name

    DB2 LOG ANALYSI

  • Fixed component ID

    5655E6601

Applicable component levels

  • R350 PSY UI54241

       UP18/03/08 P F803

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

Document Information

Modified date:
03 April 2018