IBM Support

PM76619: DOORS: Archive/Restore and Attribute DXL error '??Link module not found??'

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • You have created an attribute DXL column for the traceability
    using a Layout DXL column generated by the Analysis Wizard.
    Then, you archive and restore a module in a different database
    and when you open a module, you get '??Link module not found??'.
    
    Traceability Steps:
    1.    Analysis -? Wizard
    2.    Step 1
    a.    In-links
    b.    DOORS links
    3.    Step 2
    a.    Select formal module -? Specific (Module A)
    b.    Select link module -? Specific (Link Module)
    4.    Step 3
    a.    Select Object Text attribute
    5.    Step 4
    a.    One attribute per line
    b.    No recursive analysis
    c.    Finish
    DXL Conversion Steps:
    1.    Tools -? Support Tools -? Convert Layout DXL to Attribute
    DXL
    2.    Select ?In-links (Module A)
    3.    Response ? Success
    4.    Save View
    
    Then, Archive the project.
    
    View with Traceability on new workstation
    1.    Restored archive to another workstation using the same
    version of DOORS (9.3.0.6).
    2.    Open a module with traceability column and select
    Traceability with DXl Conversion view
    3.    Converted Layout DXL column displays ??Link module not
    found??
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The basic problem is that the generated attribute DXL code
    refers to the link module by it's unique internal ID.
    However, once you import the project into a new database,
    all of the IDs are changed, so this code can never find the
    link module.
    

Problem conclusion

  • Extended the index mapping to also process attribute DXL, in
    addition to the layout DXL
    
    Used the existing DXL mapping code,  but called on the
    attribute DXL definitions.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM76619

  • Reported component name

    TLOGIC DOORS

  • Reported component ID

    5724V61DR

  • Reported release

    930

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-11-06

  • Closed date

    2013-03-18

  • Last modified date

    2013-03-18

  • 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

    TLOGIC DOORS

  • Fixed component ID

    5724V61DR

Applicable component levels

  • R930 PSN

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYQBZ","label":"Rational DOORS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.3","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
29 October 2021