IBM Support

JR44502: MULTIPLE LOOKUP TABLES ALLOW DUPLICATE ENTRIES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a link is moved it retains the AllowDups setting, which is
    not easily reset from the GUI.
    There are some other issues with the decisions made about which
    link is used for the "Multiple rows returned from link:" setting
    in the Lookup Contraints dialog - we think that the first
    reference link with an AllowDups setting should be used, not the
    last one.
    i.e. if you add further reference links that had an AllowDups
    setting from a previous attachment, why would it change which
    link was used for this setting ?
    And the compiler should default to using any AllowDups setting
    from the first link with that setting (to match the GUI), and
    clear AllowDups from subsequent links.
    

Local fix

  • The workaround the issue is to use an additional Lookup stage,
    so  each Lookup stage will have 1 reference link.
    
    Another workaround for this customer seems to be that if the
    "Multiple rows returned from link:" setting is cleared, the
    Stage closed,
    then re-opened and the correct link chosen (or left empty if
    that is what is required), then the AllowDups generated in Osh
    is correct.
    

Problem summary

  • *************************************************************
    USERS AFFECTED:
    Users of PXLookup stages who have been chaning links
    between different Pxlookup stages and have corrupted their
    AllowMultiRow settings.
    *************************************************************
    PROBLEM DESCRIPTION:
    PxLookup stages with multiple input links incorrectly marked
    as AllowMultiRow result in incorrect Osh generated with
    multiple allow_dups options.
    *************************************************************
    RECOMMENDATION:
    Apply patch JR44502.
    *************************************************************
    

Problem conclusion

  • Apply patch JR44502.
    To fix generated OSH for affected jobs, they must be recompiled.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR44502

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    870

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-10-24

  • Closed date

    2012-12-20

  • Last modified date

    2013-03-28

  • 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

  • R870 PSY

       UP

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

Document Information

Modified date:
07 October 2021