Overview of commands
Alphabetical summary of commands
sccs and pseudo-commands
Note: SCCS users who are more familiar with RCS may benefit from the "Conversion Guide for SCCS Users" in Section 18. This lists SCCS commands and their RCS equivalents.
The Source Code Control System (SCCS) lets you keep track of each revision of a document, avoiding the confusion that often arises from having several versions of one file on line. SCCS is particularly useful when programs are enhanced but the original version is still needed.
All changes to a file are stored in a file named s.
which is called an SCCS file.
Each time a file is "entered" into SCCS,
SCCS notes which lines have been changed or deleted since the
most recent version. From that information, SCCS can regenerate
the file on demand.
Each set of changes depends on all previous sets of changes.
Each set of changes is called a
delta and is assigned an SCCS
identification string (
sid consists of
either two components, release and level numbers (in the
b), or of four components:
the release, level, branch, and sequence numbers (in the
The branches and sequences are for situations when two on-running
versions of the same file are recorded in SCCS.
126.96.36.199 refers to release 3, level 2, branch 1, sequence 1.
SCCS commands fall into several categories:
Create new SCCS files and change their parameters.
Retrieve versions of SCCS files.
Create a new version of an SCCS file (i.e., append a new
Cancel a get operation; don't create a new delta.
Change the comment associated with a delta.
Combine consecutive deltas into a single delta.
Remove an accidental delta from an SCCS file.
Print a command synopsis or clarify diagnostic messages.
Print portions of SCCS files in a specified format.
Show editing activity on SCCS files.
Search for all occurrences of the pattern get substitutes for %Z%, and print out the following text.
Show the differences between any two SCCS files.
Validate an SCCS file.