IBM Support

PI57644: RHAPSODY DOES NOT REMOVE OLD MAKEFILE HYPERLINK FROM COMPONENT AFTER ADDING VISUAL STUDIO STEREOTYPE TO CONFIG

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Description
    ========
    
    - Project began using GMR in standard MSVC configuration.
    Makefile is generated to this project.
    Component contains - _linkTarget =
    "C:\\workspace\\91707\\RhapsodyProject\\Project\\DefaultComponen
    t\\DefaultConfig\\DefaultComponent.mak";
    
    - Project config is changed to visual studio config, MSVC
    project is created, and rhapsody code is regenerated. Makefile
    is generated to MSVC project folder.
    Component still contains - _linkTarget =
    "C:\\workspace\\91707\\RhapsodyProject\\Project\\DefaultComponen
    t\\DefaultConfig\\DefaultComponent.mak";
    
    - The component .cmp file should have removed this old
    linktarget entry since it was replaced.
    
    Steps to Reproduce:
    ============
    
    1. Create Rhapsody project in \TestArea\RhapsodyProject
    2. Add a class
    3. GMR the project. Note the DefaultComponent.cmp file has
    makefile pointing to
    \TestArea\RhapsodyProject\DefaultComponent\\DefaultConfig\\Defau
    ltComponent.mak
    
    4. Change the active config to Visual Studio config.
    5. Open MSVC2010
    6. In RHP, right-click the VS Config and create IDE project
    7. In MSVC, create empty project in \TestArea\MSVCProject
    8. In Rhapsody, Regenerate the code,
    9. Note the code is being generated to MSVC directory as
    expected
    10. Note the DefaultComponent.cmp file still has makefile
    pointing to
    \TestArea\RhapsodyProject\DefaultComponent\\DefaultConfig\\Defau
    ltComponent.mak
    
    This should have been replaced with the new makeifle location
    for this config.
    
    Business Impact:
    ===========
    Exposing the old file path has potential security implications
    for customer.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Rhapsody 8.1.4                                               *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * After changing the configuration to VS configuration, the    *
    * makefile hyper link point to the new location of the         *
    * generated makefile, and also in the Hyperlink Features       *
    * dialog the shown path is correct,  but after save, the       *
    * Component repository file still has the old makefile path.   *
    * Same for the main file hyperlink. (see the field             *
    * "_linkTarget"                                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • Fixed in 8.1.5
    The repository now reflect the actual path that can be seen in
    the Hyperlink Features dialog.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI57644

  • Reported component name

    TLOGIC RHAPSODY

  • Reported component ID

    5724V74RP

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-02-19

  • Closed date

    2016-04-25

  • Last modified date

    2016-04-25

  • 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 RHAPSODY

  • Fixed component ID

    5724V74RP

Applicable component levels

  • R814 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS7P9W","label":"Rational Rhapsody"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
25 April 2016