PM40028: Incompatible Build Number error when opening profiles; rhapsody delivered profile.

Rational Rhapsody Fix Pack 8.0.2
Rational Rhapsody 8.0.6

APAR status

• Closed as program error.

Error description

• The property CompareBuildNumberInRepository is having an effect
  on profiles that are part of the Rhapsody software delivery.
  (out-of-the-box profiles).
  
  A client upgraded a project to 7.5 from 7.2.
  They set the CompareBuildNumberInRepository property in 7.5
  Then they open the project they receive the following error
  message:
  
  'Expected build number 1195120 in file
  ...$(OMROOT)/Profiles/CGSimplifiedModelProfileCpp.sbs.  Found
  incompatible build number 893528 quitting.
  
  ++++++++++
  There are a number of problems with this issue
  
  1. The definition for the property is incorrect. The information
  contradicts itself.
  2. Usuability is not friendly (see video)
  a. Create a project in 7.5.2, set the property.
  b. Open the project in 7.5.3
  c. Numerous error messages show up.
  d. Number of items come in as (U).
  e. Open the model again in 7.5.2, the default package is
  unloaded. Why?
  
  
  3. Is there a need for this property any longer know that users
  can save Rhapsody projects to a previous version?
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Incompatible Build Number error when opening profiles;
  rhapsody delivered profile.
  

Problem conclusion

• 1. the description of the property shuold be fixed2.a-2.d:
  it works as designed. the point is to align users to work
  with the same build number when working with the model.
  (setting the checkbox should be done after the model was
  saved as in the desired version)therefore units saved in
  other build numbers won't be loaded and marked with (U)2.e:
  Rhapsody saves which units were loaded in last session. this
  info is relevant if opening the model in "restore last
  session" option. Opening it from MRU is also "restore last
  session".Therefore, even if opening with correct build
  number, the units that were not loaded in previous session
  will not be loaded.In order to load all model, use the open
  dialog and select "With all subunits"3. as said in #2, the
  point is to align users to work with the same build number
  when working with the model. for example, major version and
  its MR can open the same model. The property is supposed to
  Block using different build numbers.save as previous version
  does the oposite of block. it let's users open a model in
  previous version (which if was not saved in prev version, it
  could not be opened)
  

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

• R750 PSN

     UP