A question-and-answer list.
Following
is a list of the most commonly encountered problems with their solutions:
- Question: "I checked out a controlled file,
but I am not able to change its description, properties, and so on."
Answer: The
metadata for the controlled file is stored in its parent element.
So you must check out the parent element in order to change any associated
information, such as the description and properties.
For instance, in the example provided in Adding controlled files, right-click
the parent element RailCarsPackage and choose to be able to modify the controlled file attributes.
- Question: "I know controlled files are copied
to a directory under _rpy during the creation of
the controlled file, but where exactly is the controlled file copied?"
Answer: Controlled
files are copied to the same location where its parent is located
on the disk. For instance, suppose you have a package called package_1 and
the repository file for it is stored like so: MyProject_rpy\package_1\package_1.sbs.
Now any controlled file you add to the package_1 package
is going to be stored in the folder: MyProject_rpy\package_1\
- Question: "When I open a Controlled File
Features window and try to rename the controlled file, I receive the File
not found error message."
Answer: You
can select different files from an opened Features window. So when
you type a different name, the system assumes that you are actually
trying to point to a different file and returns an error message.
You can rename a controlled file from the browser by clicking two
separate times on it (double-clicking on the file opens it).
- Question: "Is it possible to add a controlled
file to the model without copying the file to the _rpy folder?"
Answer: No,
but you can add a hyperlink to the wanted file instead. However, this
results in the loss of all configuration management capability, which
includes the following operations: - Add to archive
- Check in
- Check out
- Lock
- Unlock
- Issue: Configuration management operations
on controlled files fail on some occasions.
Details: If
you are using configuration management in command mode, make sure
that the file is located under the _rpy folder. In
order to perform Configuration Management operations in command mode
from Rational Rhapsody, the file (other than the project itself) has
to be under the _rpy directory. There is no current
fix for this issue.
Workaround: Create
a package under the project. By default, a package is stored in separate
file: do not modify that setting. Then add the problematic controlled
files to this package and are able to perform configuration management
operations.
- Issue: Adding an existing element with a
controlled file to the model and choosing a different name, instead
of replacing the file.
Details: If
you perform an Add To Model of an already existing element, Rational
Rhapsody gives you the option of replacing the element or adding it
using a different name. If you choose to use a different name, the
product adds the element using the new name.
If both the element that existed in the model and the element that
was added have controlled files by the same name, more than one controlled
file of the same name exists in the model. But there might be only
one instance of the file in the directory, which means the two controlled
files in the model are actually pointing to the same file.