IBM Support

JR57069: Connector Migration Tool does not migrate the part of WHERE clause: 'COLUMNNAME=?', that is generated by lookup operation

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

  • When a DB2 API stage (DSDB2 stage) is migrated to DB2
    Connector stage, the Connector Migration Tool (CMT) does not
    migrate the part of WHERE clause: 'COLUMNNAME=?', that is
    generated by lookup operation with reference link.
    The Connector Migration Tool (CMT) migrates only the custom
    WHERE clause as specified in: "DB2 API stage (DSDB2 stage) ->
    Output -> SQL -> Query -> Generate SELECT clause from column
    list; enter other clauses -> SQL Clauses -> Clauses -> WHERE
    clause".
    The issue has been identified in Server job with Transformer
    stage performing lookup operation.
    

Local fix

  • When the SQL statement is migrated to DB2 Connector, the option
    "Generate SQL" is set to "No", so it possible to manually add:
    COLUMNNAME=? or ORCHESTRATE.<COLUMNNAME> to the user query.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users migrating DB2 API stage (DSDB2 stage) to DB2 Connector
    stage on Server job with lookup operation.
    ****************************************************************
    PROBLEM DESCRIPTION:
    When a DB2 API stage (DSDB2 stage) is migrated to DB2 Connector
    stage, the Connector Migration Tool (CMT) does not migrate the
    'COLUMNNAME=?' part of WHERE clause, that is generated by
    lookup operation with reference link.
    The Connector Migration Tool (CMT) migrates only the custom
    WHERE clause specified in: "DB2 API stage (DSDB2 stage) ->
    Output -> SQL -> Query -> Generate SELECT clause from column
    list; enter other clauses -> SQL Clauses -> Clauses -> WHERE
    clause".
    ****************************************************************
    RECOMMENDATION:
    Apply the patch JR57069
    ****************************************************************
    

Problem conclusion

  • CMT incorrectly migrates Lookups, there is no specific code to
    handle this.
    Implemeted the fix, so the Lookup is correctly migrated.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR57069

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    B50

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-11-28

  • Closed date

    2017-01-31

  • Last modified date

    2017-01-31

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

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

Modules/Macros

  • CMT
    

Fix information

  • Fixed component name

    WIS DATASTAGE

  • Fixed component ID

    5724Q36DS

Applicable component levels

  • 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":"11.5","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
31 January 2017