IBM Support

PM50506: Clearing test plan association fails for a view, if RQMi is configured with a different instance of RQM

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Steps to Reproduce
    ==================
    1. Configure RQMi to work with RQM instance A
    2. Export a view - View A.
    3. Now, re-configure RQMi to work with RQM B
    4. Try exporting View A - FAILS
    5. Try clearing Test Plan association for View A - FAILS
    
    Note - Any new view which was not exported before re-configuring
    RQMi, will work fine.
    
    Workaround
    ==========
    On the DOORS Server machine, navigate to the ?DOORS
    Datafolder?\conf\u1000001.dir\RQM folder which holds the
    information of the views which were already exported to RQM-A.
    Look for the file having the uniqueID of the module (Module1)
    with the view (Veiw-A) in question.
    
    For example if the uniqueID of the module is 00000021, then the
    file name should look like 'Module00000021-View00000001.txt'.
    
    Rename this file and restart the DOORS client and now it should
    let us export the view (View-A) to the new RQM (RQM-B) instance.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    1. Configure RQMi to work with RQM instance A
    2. Export a view - View A.
    3. Now, re-configure RQMi to work with RQM B
    4. Try exporting View A - FAILS
    5. Try clearing Test Plan association for View A - FAILS
    
    Note - Any new view which was not exported before
    re-configuring RQMi, will work fine.
    

Problem conclusion

  • This will be addressed in the 2012 release of RQMI that
    corresponds to DOORS 9.4
    
    The RQMI Server will no longer be a required component. RM
    data in DOORS will be linked via OSLC data to QM data in
    RQM, and will be product to product with no intermediate
    components.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM50506

  • Reported component name

    TLOGIC DOORS

  • Reported component ID

    5724V61DR

  • Reported release

    920

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-10-20

  • Closed date

    2012-06-06

  • Last modified date

    2012-06-06

  • 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

  • R920 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.2","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
28 October 2021