About this task
This operation is based on properties you set depending
on whether you use batch mode or the SCC API in SCC mode.
Table 1. Controlling renaming a file| Batch mode |
SCC mode |
| Set ConfigurationManagement::ClearCase::RenameActivation.
You can set the RenameActivation property so that Rational Rhapsody does
the renaming automatically or prompts the user to confirm the action
requested. |
Set the following properties, depending on the configuration
management tool you use:- If you are using IBM Rational ClearCase®,
set ConfigurationManagement::SCC::RenameActivation and ConfigurationManagement::General::UseHybridModeWhenPossible.
You can set the RenameActivation property so that Rational Rhapsody does
the renaming automatically or prompts the user to confirm the action
requested.
- If you are using IBM Rational Synergy,
set ConfigurationManagement::SCC::RenameActivation.
You can set the property so that Rational Rhapsody does
the renaming automatically or prompts the user to confirm the action
requested.
- If you are using any other SCC tool, when you rename a package
that is in a separate directory, the product does not make any changes
to the configuration management system. Instead, Rational Rhapsody displays
an error message stating that the operation could not be executed
in the configuration management system.
If
you change the model only, the product renames the package in the
model but does not change the file system or configuration
management system. If you change the model and the file system, Rational Rhapsody changes
both the model and file system. For more information, see Failure to update the configuration management system.
|
Note: For this operation, the Undo command
(Ctrl+Z) in Rational Rhapsody works
only in the model, not in the archive. You cannot undo a rename operation
in the archive.
In cases where the product
cannot rename the file in the configuration management system, Rational Rhapsody changes
the unit name in the model, but not in the configuration management
system. For more information, see Failure to update the configuration management system.