TOC PREV NEXT INDEX DOC LIST MASTER INDEX




More on Corresponding Files (Summit/CM)

Files are said to be corresponding if they exist in different views of the same subsystem and have the same view-relative name. Corresponding files are able to share the same version history and thus have their development be coordinated.

When corresponding files share the same version history, usually only one file at a time can be checked out for editing.

Version control is described in the Command Reference.

Corresponding Files with the Same Version History

For example, Donna, Carlos, and Sam work in three different views of the same subsystem, and all three views contain units A, B, and C. Corresponding units in all views share the same version history.

Donna is responsible for developing A, but Carlos and Sam need a stable version of A to compile with as they develop B and C, respectively. Because the units are corresponding and under version control, Carlos and Sam's units remain at version 1 even after Donna creates two new versions of A.

When version 3 is ready to use, Donna tells Carlos and Sam to update their versions of A to version 3. Because all three copies of A are corresponding and share the same version history, Carlos and Sam can execute the Control > Update Objects (Apex/Summit) and Control > Update Objects (Apex/Summit) commands to do this.

There is also information on Corresponding Files with Different Version Histories.

Corresponding Files with Different Version Histories

Corresponding files do not have to share the same version history. In the diagram below, for example, file A in view1.wrk and file A in view2.wrk are corresponding, as are file view1.wrk/B and file view2.wrk/B. Because file A in both views share the same version-history family (Common), their versions are recorded in the same time-ordered sequences. Versions of B, however, are recorded in two different histories.

If view1.wrk accepts changes from view2.wrk to update the latest version, only A is updated (to version 5) because view1.wrk/B and view2.wrk/B do not share a version history.

Additional Topics

For additional information, click on a topic:


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