Checking out units

In batch mode, the Check Out operation can fetch a unit from the archive with or without a lock. However, in Microsoft Common Source Code Control (SCC) mode, the Check Out operation always fetches the unit with a lock.

About this task

In both batch and SCC modes, the Check Out operation always performs implicit Add to Model and Update operations using the appropriate configuration management information (such as version, configuration management header, and so on).

Before checking a unit out of the archive, use the List Archive option to confirm that the unit has been properly added to the archive, and that at least one version of it has already been checked in.

Procedure

  1. On the IBM® Rational® Rhapsody® browser, right-click the units you want to check out and select Configuration Management > Check Out.
    The Check Out window opens with information displayed for the selected items. If a selected item is reserved by another user, the Reserved check box is selected and the check-out operation cannot be executed.
  2. Select the Include descendents check box if you want the units checked out with nested units. For example, if a package that is a unit has a nested package that is also a unit, this option checks out both packages.
  3. Select the Include corresponding source artifacts check box, if available, if you want to check out corresponding source artifacts. (Code preserving information, such as mapping, ordering, and code snippets, of an element is defined in a SourceArtifact element, which is typically created by reverse engineering or roundtripping.
  4. If your configuration management tool has advanced options, you can click an Advanced button to open its Advanced Options window. The Advanced Options window that opens is provided by your configuration management tool.
  5. If you opened an Advanced Options window, click OK to close it after you make your selections.
  6. Click OK on the Check Out Options window to confirm your settings and check out the units.

Results

Depending on what changes you make to a unit that is contained inside a package (for example, a class), the package information might also change accordingly.

In the following situations, you must check out the containing package and the nested unit:


Feedback