Glossary

Access control
The Configuring facility by which users can control access to workspaces by Configuring commands.
Branch (SCCS)
A delta or series of deltas that are placed off of the main line of deltas in an SCCS history file.
Bringover Create
The transaction used to copy groups of files from a parent workspace to a nonexistent child workspace. The new child workspace is created as a result of the transaction. All Configuring transfer transactions are performed from the perspective of the child workspace; hence the Bringover Create transaction "brings over" files to the child from the parent workspace. See also Bringover Update, Workspace and Putback.
Bringover Update
The transaction used to update an existing child workspace with respect to files contained in its parent workspace. All Configuring transfer transactions are performed from the perspective of the child workspace; the Bringover Update transaction "brings over" files to the child from the parent workspace. See also Bringover Create, Workspace, and Putback.
Child workspace
A workspace that has a parent workspace listed in its Codemgr_wsdata/parents file. Development work is typically done in child workspaces and put back to parent workspaces after it has been tested. The Configuring transfer transactions are viewed from the child workspace perspective, and all conflicts are resolved in the child workspace.
Codemgr_wsdata directory
Every TeamWare workspace contains a "metadata" directory in its root directory named Codemgr_wsdata. Configuring stores data about the workspace in Codemgr_wsdata. The presence of this directory is the sole factor that defines it as a TeamWare workspace (as opposed to a normal directory). Configuring commands use the presence or absence of this directory to determine whether a directory is a workspace. All data stored in the Codemgr_wsdata directory is contained in flat ASCII text files that can be edited by users. See Section , "The Workspace Metadata Directory," on page 62 for more information.
Conflict
The condition that exists when a file has changed in both the child and parent workspace. Conflicts are identified by the Bringover Update transaction and are resolved by using the Resolve transaction.
Copy-Modify-Merge
The concurrent development model upon which Configuring is based. Using this model, multiple developers concurrently copy sources from a common area, modify the source in isolation, and then merge those changes with changes made by other developers.
Create
Used in Configuring transaction output. Files are said to be created if they exist in the source workspace and not in the destination workspace, and are copied into the destination workspace as part of a Bringover or Putback transaction.
Default line of work
The branch in an SCCS history file upon which the next delta will be added.
def.dir.flp
The default FLP shipped with Configuring is def.dir.flp; this FLP recursively descends directory hierarchies and lists all files for which SCCS history files exist. See FLP.
Delta
The set of differences between two versions of a file checked into SCCS. When you check in a file, SCCS records only the line-by-line differences between the text you check in and the previous version of the file. This set of differences is known as a delta. The file version that you initially checked out was constructed from a set of accumulated deltas. The terms delta and version are often used synonymously; however, their meanings are not the same. It is possible to retrieve a version that omits selected deltas. See Version.
Merging
The TeamWare utility used to merge deltas during Resolve transactions. See Chapter 9, "Resolving Conflicts," and the section on Merging.
FLP
An FLP or FIle List Program is a program or script that generates a list of files to stdout that Configuring then processes during Bringover and Putback transactions. See def.dir.flp.
FreezePointing
The TeamWare utility used to make snapshots of workspaces (or portions of them) at important junctures or "freezepoints."
g-file (SCCS)
The working copy of a file retrieved from an SCCS history file by the sccs-get command.
History Files
When you initially put a file under SCCS control, a history file is created for the new SCCS file. The initial version of the history file uses the complete text of the source file. The initial history file is the file that further deltas are compared to. Owing to its prefix (s.), the history file is often referred to as the s.file (s-dot-file).
Integration workspace
A workspace to which multiple developers put back (merge) their work.
Lock
To assure consistency, the Configuring file transfer transactions Bringover and Putback lock workspaces while they are working in them. Locks are recorded in the Codemgr_wsdata/lock file in each workspace; the Configuring commands consult that file before acting in a workspace. See read-lock, write-lock.
Merge
To produce a single version of a file from two conflicting files (deltas). Usually accomplished with the assistance of the Merging program.
Notification
A Configuring facility that mails notice of events, such as changes to files or directories, to users.
Parent workspace
A workspace that has a child workspace(s) listed in its Codemgr_wsdata/children file. Parent workspaces are typically used as integration areas, since development, testing, and conflict resolution occur in child workspaces.
ParallelMake
The program distributed as part of TeamWare that enables program builds to be parallelized over multiple processes and CPUs. See the section on ParallelMake.
Putback
The transaction used to update a parent workspace with respect to files contained in its child workspace. All Configuring transfer transactions are performed from the perspective of the child workspace; the Putback transaction "puts back" files to the parent from the child workspace. See also Bringover Create, Bringover Update, and Workspace.
Read-lock
A lock that is obtained by a Configuring command while it examines the contents of a workspace. A read-lock assures that the workspace does not change while the command is examining files in a workspace. Read-locks may be obtained concurrently by a number of commands; no Configuring command may write to the workspace while a read-lock is in force. See lock, write-lock.
Reparent
To change the parent of a child workspace.
Resolve
To produce a new delta of a file from two conflicting deltas. See merged, conflict.
Root directory
The top-level directory of a Configuring workspace. This directory's path name is the name by which the workspace is referred.
SCCS Delta ID (SID)
A SID is the number used to represent a specific delta. This is a two-part number, with the parts separated by a dot (.). The SID of the initial delta is 1.1 by default. The first part of the SID is referred to as the release number, and the second, the level number. When you check in a delta, the level number is incremented automatically.
SCCS history file
The file that contains a given file's delta history; also referred to as an "s-dot-file." All SCCS history files must be located in a directory named SCCS, which is located in the same directory as the g-file. See g-file.
SID
SCCS delta ID--The number used to represent a specific SCCS delta.
Undo
To return a workspace to the state it was in before the most recent Bringover or Putback transaction, thereby "undoing" the action of the transaction.
Update
Files are said to be updated during a Bringover or Putback transaction if they exist in both the source workspace and in the destination workspace, and have changed in the source workspace. The SCCS history file in the destination workspace is updated with new deltas from the source workspace.
Version
When you check in a file, SCCS records only the line-by-line differences between the text you check in and the previous version of the file. This set of differences is known as a delta. The file version that you initially checked out was constructed from a set of accumulated deltas. The terms delta and version are often used synonymously; however, their meanings are not the same. It is possible to retrieve a version that omits selected deltas. See Delta.
Versioning
The TeamWare program that provides a graphical interface to SCCS. See the section on Versioning.
Workspace
A workspace is a specially designated (but standard) directory and its subdirectory hierarchy. Usually each developer on a project works in their own isolated workspace concurrently with other developers programming in other workspaces. Configuring provides utilities to "intelligently" copy files from workspace to workspace.
Workspace hierarchy
A hierarchy of parent and child workspaces in which programmers and release engineers can develop, test, share, and release software products.
Write-lock
A lock that is obtained by a Configuring command that changes data in a workspace. Only one write-lock may be obtained for a workspace at any time. When a write-lock is in force, only the Configuring command that owns the lock may write to the workspace; other commands cannot obtain read-locks from the workspace. See lock, read-lock.