PI73901: UNEXPECTED TIMESTAMPS IN MODEL FILE AFTER MERGE

IBM Rational Rhapsody 8.2.1

APAR status

• Closed as program error.

Error description

• We maintain our model fragments in RTC SCM, therefore we have
  disabled
  the timestamps in the model files by setting:
  Property SupportIncrementalModelSynchronization Bool "False"
  Property IncrementalCodeGenAcrossSession Bool "False"
  as these timestamps cause a lot of "noise" in a file based SCM.
  
  While this works fine in Rhapsody itself, the Merge tool does
  not
  correctly handle these settings, after a merge timestamps
  re-appear in
  the model file.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Rhapsody                                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Mentioned properties are overridden on project level. When   *
  * diffMerge compares separate units (e.g. packages) it cannot  *
  * access these overridden values.                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• General::SupportIncrementalModelSynchronization and
  General::Property IncrementalCodeGenAcrossSession preferences
  are added to DiffMerge preferences (see their default values in
  factory.prp's DiffMerge subject section). User should set them
  to False (switch off these preferences) to solve the 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

• R815 PSN

     UP