Rewriting the work area

About this task

The sync command completely rewrites a work area for a project. The default directory in which all project work areas are created is ccm_wa followed by the database name in your home directory. Use the sync command to manually synchronize the work area.

Note: Only a build manager or a user in the ccm_admin role can sync a non-writable project.
ccm sync [-r|-recurse] [-nr|-norecurse|-no_recurse] [-s|-static]
         [-p|-project] project_spec...
-nr|-norecurse|-no_recurse
Specifies not to recurse the project hierarchy during the project sync. Synchronize only the specified project.
This is the default.
-p|-project project_spec...
Specifies the project that you want to synchronize.
You can specify one or more arguments that are project specifications; each can specify one or more projects. See Project specification for details.
-r|-recurse
Causes all objects in the project hierarchy to be sync’d along with the specified project.
-s|-static
Updates an existing static work area with current data from the database. (A static work area is a local copy of the work area for a static subproject.) In addition, updates all static work areas in the hierarchy for which the ccm sync command was issued. This fully synchronizes all static work areas in the hierarchy by using one command. If no static work area exists in the hierarchy, this option is ignored.

Examples

About this task

  • Synchronize the work area for toolkit-linda and its subprojects.

    ccm sync -recurse -project toolkit-linda

  • Create a work area for the specified project.

    ccm sync -p ico_aug1-1

Defaults

About this task

You can set these related options in your ccm.ini file (Windows) or .ccm.ini file (UNIX):

Description and uses

About this task

Your work area is created automatically when you create a project and when you check out a project using the check out commands. As you add new members to your project, your work area is updated automatically.

You will need to manually sync (force a sync) your work area in these cases:

  • You "clean out" (delete) any or all objects in your work area.

    When you force a sync, only the necessary (controlled) objects from your database are written out to your work area.

  • The work_area command fails while changing your work area path.

    When you change your work area path either from the CLI or the GUI, Rational Synergy will try to update your work area path to the new location. If another application is using the old work area path, the move will fail and you will need to synchronize your work area.

  • You change your work area type from one that uses local copies to one that uses symbolic links (or vice-versa).

    If you want to change your work area type:

  • Reconcile the work area that you are currently using (either local copies or symbolic links).
  • Delete the work area objects from the file system.
  • Set your work area path and options.
  • Start a new session using the client option of choice (either local copies or symbolic links).
  • Re-create your work area by forcing a sync (execute the sync command).
    Note: To stop a sync from the CLI, enter CTRL+C at any time.
    Note: If you stop the sync, you will receive an error message stating that errors may occur in your work area. The errors will not occur until you try to use the work area; to avoid problems, perform a complete synchronization of the work area before you use it.

Feedback