Commands available on elements in read-write mode

Overview

Elements in read-write mode can be directly modified. The available commands are used to make these elements non-modifiable, by integrating the modifications into the repository ("Check-in") or by cancelling the modifications carried out ("Undo check-out").

Figure 14. Representation of elements in read-write mode

Check-in

This command is used to check-in and export the unit which was previously reserved or which you have just created.

At the end of this operation, those elements on which the command has been run are unlocked and can be reserved by another user.

This command can only be run on components that have been checked-out.

When the "Check-in" command is run on the elements concerned, they are subsequently put into read-only mode.

In certain cases, units which depend on other units, on which a check-out is requested, can be automatically checked-in, in order to make the project consistent with the repository. For example, a new unit cannot be checked-in, in order to retain the composition between units in the multi-user repository.

For the Objecteering Multi-user and Objecteering ClearCase MDACs, if the element has not been modified, then an "Undo check-out" is automatically run, instead of a check-in. This means that the element's version is not incremented if the element is identical to the previous version.

For the Objecteering ClearCase, Objecteering SCC and Objecteering Dimensions MDACs, a comment can be entered on the check-in. A dialog box is displayed; if the "Confirm operations" MDAC parameter has been activated and the element has been modified (if this is not the case, another check-out is carried out and no comment is requested).

Figure 15. Comment entry dialog box for a check-in

The "Store the comment for the whole session" tickbox allows you to apply the same comment or a different comment to all the components. Where the check-in is carried out hierarchically, the comment entered the time before is then re-used.

Note: Clicking on the "Cancel" button cancels the check-in for the current unit and all the following units.

Involuntary interruption of a Check-in

If a check-in operation is interrupted (due to a power cut or a network problem, for example), the repository is restored to its last state before the check-in was launched. This restoration occurs the next time a Multi-user command is run, or when the database is opened in the case of a power cut. In the meantime, the repository is locked and import operations cannot be carried out.

In order to do this, the MDAC creates a directory named "/Lock/userName" every time a check-in operation is run. This directory contains a directory structure which can be used to cancel the check-in. We strongly recommend against destroying the "userName.write" file in the "Locks" directory if a "userName" sub-directory exists.

Check-in and check-out

This command is used to check-in and export a unit into the repository, thereby making it available to other users working on the multi-user project, and then to check-out this unit once again, in order to continue working on it.

This command can only be run on checked-out components.

For further information, please refer to the "Check-in" and "Check-out" commands.

Undo check-out

This command is used to undo the check-out of the element and abandon the reservation. The repository is not updated, but elements for which the check-out has been cancelled are re-imported into the Objecteering modeling project, in order to retrieve their latest version.

At the end of this operation, those elements on which the command has been run are unlocked and can be reserved by another user.

This command can only be run on checked-out components.