IBM Support

JR58006: DB2 CONNECTOR: NO GENERATION OF EVENTS FOR OPERATIONAL METADATA DEPENDING ON SQL PROVIDED AS PARAMETER

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • A DB2 Connector includes a  user-defined SELECT statement
    included a WHERE with the WHERE provided as job parameter.
    This DB2 Connector could not generate the informaton linked to
    this SELECT in the event file for the Operational Metadata for
    a job run.
    This was the case for the value of the  job parameter as
    "(1=1)".
    

Local fix

  • Change the user defined SELECT to not include control
    characters in the job parameter value.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users wishing  to generate Operational Metadata XML event on
    user defined SQL queries
    ****************************************************************
    PROBLEM DESCRIPTION:
    DB2 connector does not generate table information for events in
    Operational Metadata XML. As a result, lineage is not available
    for the DB2 connector job.
    
    DB2 Connector does not generate locator information for
    Operational Metadata XML when a complex user-defined SQL is
    used, for example with sub-select statements or join clauses.
    The problem occurs also when user-defined SQL uses job
    parameters to parametrize not only column values, but larger
    parts of the query, for example:
    SELECT * FROM TABLE_A WHERE #PARAM#
    PARAM = "TABLE_A.COLUMN_B = 'something'"
    ****************************************************************
    RECOMMENDATION:
    Apply patch JR58006.
    ****************************************************************
    

Problem conclusion

  •  Problem is caused by the fact that SQL builder does not return
    information about tables that the user-defined SQL operates on,
    so DB2 connector passed an empty table list to the Operational
    Metadata XML.
    DB2 connector code has been changed to parse user-defined SQL
    queries to retrieve the working table list without relying on
    SQL builder.
    

Temporary fix

  • n/a
    

Comments

APAR Information

  • APAR number

    JR58006

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    912

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-06-09

  • Closed date

    2017-08-29

  • Last modified date

    2017-08-29

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

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

Fix information

  • Fixed component name

    WIS DATASTAGE

  • Fixed component ID

    5724Q36DS

Applicable component levels

  • R912 PSY

       UP

  • RB31 PSY

       UP

  • RB50 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"IBM InfoSphere DataStage"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"912","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
29 August 2017