PI57020: UNABLE TO MERGE TWO SEQUENCE DIAGRAM WHILE DOING THREE WAY COMPARISON WITH BASE UNIT.

IBM Rational Rhapsody 8.2

APAR status

• Closed as program error.

Error description

• It is observed that while doing three way merging with base unit
  , sequence diagrams are not merged completely in the output
  model.Only system border and instance line is visible but there
  are no messages merged.
  
  Steps to Reproduce:
  1>There are three models left,right and base
  2>In left model add one class to the default package and add one
  attribute to the class.
  3>Add a sequence diagram to the model with one system border and
  two instance line with with some messages.
  4>In right model add one class to the default package.
  5> Add a sequence diagram to the model with one system border
  and two instance line with with some messages.
  6> Copy the sequence diagram and add to the model with renaming
  it.
  7>In the base model add one class to the default package and .
  8>Add a sequence diagram to the model with one system border and
  two instance line with with some messages.
  9>In diffmerge tool file->compare->select perform three way
  comparison with base unit.
  10>Give left, right and base model path.
  11>Start merge
  12>One pop up will come do you want to automatically merge all
  trival difference->Select yes
  13>File->save merge as and save the output file.
  14>While opening the output file in sequence diagram only system
  border and instance line are shown but the messages are not
  merged.
  

Local fix

• NA
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Rhapsody users                                               *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Existing SD name was changed and new SD with the name of     *
  * existing one was created. It confused diffMerge tool,        *
  * because it compares these elements by name.                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• Fixed in Rhapsody 8.2 - New DiffMerge
  General::UseGUIDforMatching preference is added, which forces
  DiffMerge using GUIDs instead of names for comparison. By
  default it is unchecked. user should check it to solve this
  specific problem.
  

Temporary fix

Comments

APAR Information

• 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

• R812 PSN

     UP