PM53709: CTE AND RSARTE INTEGRATION NOT PROVIDING LOGICAL MODEL MERGE DIALOG LEADING TO CORRUPTED MODELS.

Rational ClearCase Fix Pack 03 (8.0.0.3) for 8.0
Rational ClearCase Fix Pack 11 (8.0.0.11) for 8.0
Rational ClearCase Fix Pack 12 (8.0.0.12) for 8.0
Rational ClearCase Fix Pack 13 (8.0.0.13) for 8.0
Rational ClearCase Fix Pack 14 (8.0.0.14) for 8.0
Rational ClearCase Fix Pack 15 (8.0.0.15) for 8.0
Rational ClearCase Fix Pack 16 (8.0.0.16) for 8.0
Rational ClearCase Fix Pack 17 (8.0.0.17) for 8.0
Rational ClearCase Fix Pack 18 (8.0.0.18) for 8.0
Rational ClearCase Fix Pack 19 (8.0.0.19) for 8.0
Rational ClearCase Fix Pack 20 (8.0.0.20) for 8.0
Rational ClearCase Fix Pack 21 (8.0.0.21) for 8.0

APAR status

• Closed as program error.

Error description

• When using RSARTE and ClearCase ClearTeam Explorer(CTE)a user
  performs an operation that requires a merge(deliver/merge search
  etc) from
  source view to target view, and if the model that is present in
  the UML perspective IS NOT that of the view that is the merge
  target, the logical model merge tool does not display and merges
  proceed as if they
  were trivial and models become potentially corrupt.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The issue in question occurs only on unix platforms when the
  workbench is running in a view context.  The customer had
  symlinks of the nature /vob/vobtag/some/path --?
  /vob/othervobtag/some/path.  In the version of CTE being
  used, even when running in a view context, imported projects
  would have the path:
  /view/viewtag/vob/vobtag/some/path/projectname the
  ClearCase back end server,  of course would not know about
  the view context as this use case was not truly supported,
  so it ended up looking for the absolute path without having
  a view context.  Naturally it could not find the symlink
  target.  The fix for this deals with this.  The project set
  problems were also due to this effect although not directly
  caused by the ccbe back end.
  

Problem conclusion

• A fix is available in ClearCase versions  8.0.0.3
  

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

  CLEARCASE UNIX

• Fixed component ID

  5724G2901

Applicable component levels

• R712 PSN

     UP