IBM Support

JR51062: IMPORTING DISCOVERY DBM FILE INTO IMAM CREATES WRONG SET OF KEYS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Importing DISCOVERY dbm file into IMAM creates wrong set of keys
    

Local fix

Problem summary

  • Import using DBM File metabroker is not able to render enforced
    property for foreign key
    

Problem conclusion

  • Discovery Metabroker is ignoring the property "enforced". In the
     IDA metabroker, this property is ignored but in the Discovery
    Metabroker it is a very import piece of information that is used
     to differentiate between real keys from the inferred keys in
    the dbm file. All the keys with the enforced=false should
    be imported as inferred keys and the keys with enforced=true
    should be imported as foreign keys.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR51062

  • Reported component name

    INFO SRVR PLATF

  • Reported component ID

    5724Q3612

  • Reported release

    912

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-08-20

  • Closed date

    2016-03-14

  • Last modified date

    2016-03-14

  • 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

    INFO SRVR PLATF

  • Fixed component ID

    5724Q3612

Applicable component levels

  • R912 PSY

       UP

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

Document Information

Modified date:
08 January 2022