PM72482: modifying project's version doesn't sync the project to the new path depending on the release.

Rational Synergy Fix Pack 7 (7.1.0.7) for 7.1
Rational Synergy Fix Pack 4 (7.2.0.4) for 7.2
Rational Synergy Fix Pack 6 (7.2.0.6) for 7.2
Rational Synergy Interim Fix 3 for 7.1.0.7
Rational Synergy Interim Fix 4 for 7.1.0.7
Rational Synergy Interim Fix 1 for 7.2.0.6
Rational Synergy Interim Fix 2 for 7.2.0.6
Rational Synergy Interim Fix 5 for 7.1.0.7
Rational Synergy Fix Pack 7 (7.2.0.7) for 7.2
Rational Synergy Interim Fix 1 for 7.2.0.7
Rational Synergy Interim Fix 2 for 7.2.0.7
Rational Synergy Interim Fix 3 for 7.2.0.7

APAR status

• Closed as program error.

Error description

• Tested with Synergy 7.1.0.6.001
  -Linux server
  -Windows client
  
  
  To sum up:
  Set the  workarea's project_subdir_template to
  '%project_version\%release'.
  Modify the version of a project in CLI.
  -If the Release does not have Component name, for example with
  the release '1.0', then it works
  -If the Release has a Component, for example 'gg/1.0', then it
  does not work
  
  
  Details:
  1) Start a Synergy session with Traditional Mode
  
  2) Create  a project called for example 'lec002' with version
  'armelle5' and release 'gg/1.0'.
  ---Component 'gg'
  ---Component Release '1.0'
  
  3) Set the  workarea's project_subdir_template to
  '%project_version\%release'.
  
  4) Change the project's version using the following command for
  example:
  ###
  ccm attr -m version -v 'armelle6' -project
  lec00-armelle5:project:cent710#1
  ###
  
  The following Warning is returned:
  ###
  Not updating work area path for project 'lec00-armelle5'. Its
  work area path
  'c:\temp\ccm_wa\centos710\armelle5\gg\1.0' is incompatible with
  its project_subdir_template
  '%project_version\%release'.
  ###
  
  => The Version of the project changed.
  => The Project was not synced to the new path.
  
  
  5) Changed the project's path using the command:
  ###
  ccm wa -wa -pst '%project_version\%release' -p
  lec00-armelle6:project:cent710#1
  ###
  
  This command returns the Warning:
  ###
  Warning: Project 'lec00-armelle6' work area path
  'c:\temp\ccm_wa\centos710\_no_context_'
  is incompatible with its project_subdir_template
  '%project_version\%release'.
  Displaying default template.
  Setting path for work area of 'lec00-armelle6' to
  'c:\temp\ccm_wa\centos710\armelle6\gg\1.0'...
  Saved work area options for project: 'lec00-armelle6'
  ###
  
  => The Workarea is set correctly although there is the Warning.
  
  
  6) Additional Info:
  --The exact same steps as above with a project using a Release
  without a Component name work.
  For example, it works with the release '1.0'.
  
  --It works also with the Web mode in CLI whatever the release.
  
  --It works with a Linux client.
  
  
  7) With the following configuration:
  -Windows 2003 server
  -Windows 2003 client.
  
  a) With Synergy 7.1.0.6.001, with this configuration the problem
  occurs with the Classic client AND with the CLI in Web mode.
  
  
  b) With Synergy 7.1.0.6.001, with this configuration, 'ccm attr
  -m version -v ....' changes the version but does not sync the
  W.A.
  
  So if you use the following command to sync the project after
  the version was changed, to sync the project:
  ##
  ccm wa -wa -pst '%project_version\%release' PROJECT_OBJECTNAME
  ##
  (replace of course PROJECT_OBJECTNAME)
  
  
  -With the Classic client, there is a Warning, but the W.A is
  properly synced in the correct path.
  For example:
  ###
  ccm wa -wa -pst '%project_version\%release'
  lec02-armelle1:project:1
  Warning: Project 'lec02-armelle1' work area path
  'c:\tmp\ccm_wa\win2003710\_no_context_'
  is incompatible with its project_subdir_template
  '%project_version\%release'.
  Displaying default template.
  Setting path for work area of 'lec02-armelle1' to
  'c:\tmp\ccm_wa\win2003710\armelle1\gg\1.0'...
  Saved work area options for project: 'lec02-armelle1'
  ###
  => You can see here that the new W.A is:
  c:\tmp\ccm_wa\win2003710\armelle1\gg\1.0
  
  
  -With the CLI in Web mode, the W.A is synced IN the previous
  W.A.
  Which is obviously wrong.
  For example:
  ###
  ccm wa -wa -pst '%project_version\%release'
  lec02-armelle2:project:1
  Warning: Project 'lec02-armelle2' work area path 'c:\documents
  and settings\gperrin\ccm_wa\win2003710\_no_context_'
  is incompatible with its project_subdir_template
  '%project_version\%release'.
  Displaying default template.
  Setting path for work area of 'lec02-armelle2' to
  'c:\tmp\ccm_wa\win2003710\armelle1\gg\1.0\armelle2\gg\1.0'...
  Saved work area options for project: 'lec02-armelle2'
  ###
  
  => You can see here that the new W.A is in the previous W.A:
  c:\tmp\ccm_wa\win2003710\armelle1\gg\1.0\armelle2\gg\1.0
  
  It should have been:
  ##
  c:\tmp\ccm_wa\win2003710\armelle2\gg\1.0
  ##
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  modifying project's version doesn't sync the project to the
  new path depending on the release.
  

Problem conclusion

• Fixed in Rational Synergy 7.1.0.7 and planned for Rational
  Synergy 7.2.0.4
  

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 SYNERGY

• Fixed component ID

  5724V66SN

Applicable component levels

• R710 PSN

     UP