Troubleshooting shared projects

If you have problems using shared projects, consider looking for the following problems.

Directories containing incomplete changes

The automatic directory check-in feature can cause directories to contain incomplete changes if the directory is checked out a second time before the first change is finished. For example, Bob is assigned a task to remove the file foo.c in the src directory. He deletes foo.c, which checks out and immediately checks in the src directory. He then removes references to foo.c in other objects. Before Bob completes the task of removing the references, Ann moves a file from the src directory to another directory. The src directory is checked out and immediately checked back in. Ann completes the task. The build manager updates the prep project, which uses both Ann’s and Bob’s changes, even though Bob has not completed his changes.

Incomplete changes are displayed as configuration conflicts in the prep project. This conflict can be avoided if the build managers show the conflicts after updating prep projects.

Excessive busy state

In a shared project, Rational® Synergy updates all dialog boxes affected by a change immediately following the change. This behavior can cause your interface to be busy while another user's operation is in progress.

For example, when Bob checks out an object that is in Ann’s Project pane, Ann sees the busy cursor momentarily while the object is being updated. The busy cursor is not noticeable. This behavior prevents any changes to the object while it is being updated. However, if a user performs an operation that changes numerous objects (for example, an update), the cumulative effect of the changes can result in a persistent busy cursor. The cursor flickers on and off, making it difficult to use any dialog boxes.

Because user interfaces can be rendered temporarily unusable during change-intensive operations, avoid performing such operations during peak hours.


Feedback