TOC PREV NEXT INDEX DOC LIST MASTER INDEX



Using ClearCase for Control and Configuration Management (Apex/ClearCase)

This module describes using Apex/ClearCase for control and configuration management . A file's development is tracked by saving a version of the file every time it is checked into a ClearCase VOB.

Prerequisite for this Module

Topics in this Module

Average Time to Complete this Module

15 minutes.


The Purpose of Control and Configuration Management

Placing a file under version control tracks the file's development in the ClearCase VOB(s) by saving different versions of the file as it is developed. Making files elements of the VOB allows multiple developers to easily develop and have visibility to the same set of files, each of which may be under different stages of development. For more information on ClearCase, please see the ClearCase User's Guide.


Checking Objects In and Out

By default, controlled objects are not modifiable, although you can compile against controlled objects. To make a controlled object modifiable, you must check out the object using the CM > Checkout command.

Once you have checked out an object, you can make changes to it, save it, and make more changes. None of these changes are reflected by the ClearCase VOB(s) until you check the object in, using the CM > Checkin command.


Controlling Objects

You will use the file, hello.2.ada, which you created in the "Editing, Compiling, and Executing an Ada Program (Apex/ClearCase)" module, in this exercise.

If you are not using an Apex compiler, follow the instructions to create these files using your own compiler/editor.

The steps below instruct you to place the file hello.2.ada under ClearCase control. Next, you will check out the object, modify the file, and check the file back in.

1. . Select (highlight) hello.2.ada in the directory viewer of /vobs/test/test.rss/hello.2.ada. The directory viewer can be displayed using the File > Open command.

2. . Select CM > Make Element.

3. . The Place object(s) under ClearCase control dialog box is displayed. If you did not control your Rational subsystem yet, you need to select the Control enclosing subsystem check box or you will not be able to control this object. All controlled objects must be within Controlled Rational Subsystems. Use the default settings of the controls in the dialog box. Click the OK button.

The Jobs window displays the control job.

The Message window displays a log of the command.

The file is now an element of the /vobs/text VOB meaning it is controlled and it is also checked in.


Displaying Summit/CM Attributes and Check Out

1. . With hello.2.ada selected in the directory viewer, select the View > Format > Cm Attributes command.

The display in the directory viewer changes to show the control and configuration management information. Your display looks like this:

2. . Execute the CM > Checkout command to check out the file for updating. Use the default options in the ClearCase Check Out dialog box .

The Check Out dialog box is displayed with hello.2.ada selected in the Objects to Check Out field.

3. . You are going to use the defaults so click on OK.

The file hello.2.ada is now checked out.


Abandoning Changes Using Uncheckout

Using the Control > Uncheckout command cancels your checked-out version of a file without creating a new version of the file in the Summit/CM database.

1. . With hello.2.ada still selected in the directory viewer, select Control > Uncheckout.

2. . The Uncheckout dialog box is displayed with hello.2.ada in the file-selection field.

3. . Click on OK.

When you uncheckout a checked-out file, the checkout is canceled. An option exists that allows you to save the text of the file, if desired.

For more information, see the ClearCase User's Guide.


Checking Out, Modifying, and Checking In

1. . With hello.2.ada selected in the directory viewer, select Control > Checkout. and click on OK to check out the file.

2. . If the file is not open in a text editor, open it by selecting File > Open or double-clicking on the filename.

3. . Edit hello.2.ada. For example you could add a line anywhere in the code:

Additional information is available on using the editor.

4. . Select Control > Checkin in the editor window.

5. . Click on OK in the Checkin dialog box.

The file is time-stamped when the version is checked in.

    Note: You should select the Preserve modification time of objects check box when you are working with Ada files so that Apex/ClearCase does not perform unnecessary consistency check next time it compiles the unit.

6. . You now have a controlled, checked in file on the main branch of an element in a Rational subsystem. With hello.2.ada selected in the directory viewer, select View > Format > CM Attributes.

The display should reflect that there are two versions of hello.2.ada on the main branch and that the file is checked in.

You have just completed the Control and Configuration Management Module for Apex/ClearCase. Please close all the windows you opened for this module.


Rational Software Corporation 
http://www.rational.com
support@rational.com
techpubs@rational.com
Copyright © 1993-2001, Rational Software Corporation. All rights reserved.
TOC PREV NEXT INDEX DOC LIST MASTER INDEX TECHNOTES APEX TIPS