control records are stored in the body along with the original text records. SCCS basic commands SCCS provides a set of commands in the form of macro invocations that perform or initiate source code management functions with a simple syntax, such as create, get, edit, prt. It also provides access to the revision history of files under management. These commands are implemented as argument verbs to the driver program sccs. Create The sccs command create uses the text of a source file to create a new history file. For example: $ sccs create program.c program.c: 1.1 87 lines The outputs are name, version and lines. The command is a macro that expands to admin to create the new history file followed by get to retrieve the file. Edit $ sccs edit program.c 1.1 new delta 1.2 87 lines Edit a specific file. The command is a macro that expands to get -e. Delget $ sccs delget program.c comments? main function enhanced 1.2 10 inserted 0 deleted 87 unchanged 1.2 97 lines Check in new version and get the new version from sccs. The command is a macro that expands to delta to check in the new version file followed by get to retrieve the file. Get $ sccs get program.c 1.1 87 lines The outputs are version and lines you want to get from specific file. Prt $ sccs prt program.c This command produces a report of source code changes. Implementations UNIX SCCS versions Most UNIX versions include a version of SCCS, which, however, is often no longer actively developed. Jörg Schilling's fork The late (who requested the release of SCCS in the early days of the OpenSolaris project) maintained a fork of SCCS that is based on the OpenSolaris source code. It has received major feature enhancements but remains compatible with the original SCCS versions unless using the "new project" mode. Heirloom Project The Heirloom Project includes a version of SCCS derived from the OpenSolaris source code and maintained between December 2006 and April 2007. GNU conversion utility GNU offers the SCCS compatible program GNU CSSC ("Compatibly Stupid Source Control"), which is occasionally used to convert SCCS archives to newer systems like CVS or Subversion; it is not a complete SCCS implementation and not recommended for use in new projects, but mostly meant for converting to a modern version control system. Other version control systems Since the 1990s, many