IBM Support

PI58131: UNABLE TO SHOW THE CONFLICT FOR THE ATTRIBUTE TYPE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • - create a new model, containing a class
    - This model is our Base Model.
    - Duplicate this model into two new models, LeftModel and
    RightModel.
    - Edit LeftModel, by creating an Attribute named "attribute_0 in
    the
    class, set the Attribute type to Existing boolean
    - Edit RightModel, by creating an Attribute named "attribute_0"
    in the
    class, set the Attribute type to Existing int
    - Now use DiffMerge.exe on Left, Right, Base, do automatic
    trivial
    differences. No conflict is reported.
    -In comparison view if we right click on the class and report
    difference , then it is reporting the difference for the
    attribute that one is bool and one is int.
    -But while doing the merge automatically for all trivial
    difference, it does not show this as a defect.
    -But if we change the attribute type to userdefined type , then
    it is showing as a difference and while merging it is showing a
    conflict also.
    

Local fix

  • Work around: If we donot allow automerge, then this attributes
    are shown as conflict.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Rhapsody users                                               *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * UNABLE TO SHOW THE CONFLICT FOR THE ATTRIBUTE TYPE           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • Fixed in Rhapsody 8.2 - DiffMerge shows conflict and asks user
    to solve it manually. It still recognizes new attributes of
    different types, which were added on both sides. It is correct,
    because base class doesn't contain such attribute.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI58131

  • Reported component name

    TLOGIC RHAPSODY

  • Reported component ID

    5724V74RP

  • Reported release

    810

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-02-26

  • Closed date

    2016-12-05

  • Last modified date

    2016-12-05

  • 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

  • R810 PSN

       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.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
05 December 2016