Work area conflicts occur in these cases:
Additional errors can occur with controlled links and symbolic links and the work area paths. You must manually resolve these types of conflicts.
A few other ways to use this command with files that are checked out include:
For example, if you are not running a session but you must modify a non-modifiable object, you can change the object in your work area. You can update the database later by resetting the Read Only attribute on the file and modifying it. Later, when you start a session, use the reconcile command to update your database with the work area changes.
When you stop the reconcile from the CLI, a message displays stating that errors might occur in your work area. The errors do not occur until you try to use the work area. To avoid problems, reconcile the work area before you use it.
Some operations perform some reconcile actions automatically:
The corresponding work area is examined for work area conflicts. Where possible, changes to the work area are used to update the database automatically.
The database is updated with the changed file contents from the work area.
The updated work area contents are used to update the checked out file.
Any projects that are modifiable by you that use that file and that have work areas that are visible and modifiable are updated with the new contents. The update occurs when the database is either updated explicitly by a ccm reconcile command, or automatically as part of other operations.
The reconcile command supports these subcommands.