sccsfile(4) DG/UX 4.30 sccsfile(4)
NAME
sccsfile - format of SCCS file
DESCRIPTION
An SCCS file is an ASCII file. It consists of six logical
parts:
checksum
delta table
information about each delta
user names
login names and/or numerical group IDs of
users who may add deltas
flags definitions of internal keywords
comments arbitrary descriptive information about the
file
body the actual text lines intermixed with control
lines
Throughout an SCCS file there are lines that begin with the
ASCII SOH (start of heading) character (octal 001). We call
this character the control character and represent it
graphically as @. Any line described below that does not
begin with the control character is prevented from doing so.
Entries of the form DDDDD represent a five-digit string (a
number between 00000 and 99999).
Each logical part of an SCCS file is described in detail
below.
Checksum
The checksum is the first line of an SCCS file. The
form of the line is:
@hDDDDD
The value of the checksum is the sum of all characters,
except those of the first line. The @h provides a
magic number of (octal) 064001.
Delta table
The delta table consists of a variable number of
entries of the form:
@s DDDDD/DDDDD/DDDDD
@d <type> <SCCS ID> yr/mo/da hr:mi:se <pgmr> DDDDD DDDDD
@i DDDDD ...
Licensed material--property of copyright holder(s) Page 1
sccsfile(4) DG/UX 4.30 sccsfile(4)
@x DDDDD ...
@g DDDDD ...
@m <MR number>
.
.
.
@c <comments> ...
.
.
.
@e
The first line (@s) contains the number of lines
inserted/deleted/unchanged. The second line (@d)
contains the type of the delta (currently, normal: D,
and removed: R); the SCCS ID of the delta; the date and
time of creation of the delta; the login name
corresponding to the real user ID at the time the delta
was created; and the serial numbers of the delta and
its predecessor
The @i, @x, and @g lines are optional; they contain the
serial numbers of deltas included, excluded, and
ignored, respectively.
The @m lines (optional) each contain one MR number
associated with the delta; the @c lines contain
comments associated with the delta.
The @e line ends the delta table entry.
User names
The list of login names and/or numerical group IDs of
users who may add deltas to the file, separated by
new-lines. The lines containing these login names
and/or numerical group IDs are surrounded by the
bracketing lines @u and @U. An empty list lets anyone
to make a delta. Any line starting with a ! prohibits
the succeeding group or user from making deltas.
Flags
Keywords used internally (see admin(1) for more
information on their use). Each flag line takes the
form:
@f <flag> <optional text>
The following flags are defined:
@f t <type of program>
@f v <program name>
@f i <keyword string>
@f b
Licensed material--property of copyright holder(s) Page 2
sccsfile(4) DG/UX 4.30 sccsfile(4)
@f m <module name>
@f f <floor>
@f c <ceiling>
@f d <default-sid>
@f n
@f j
@f l <lock-releases>
@f q <user defined>
@f z <reserved for use in interfaces>
The t flag defines the replacement for the %Y%
identification keyword. The v flag controls prompting
for MR numbers as well as comments; if the optional
text is present it defines an MR number validity
checking program.
The i flag controls the warning/error aspect of the No
id keywords message. When the i flag is not present,
this message is only a warning; when the i flag is
present, this message will cause a fatal error; the
file will not be gotten, or the delta will not be made.
When the b flag is present the -b keyletter may be used
on the get command to cause a branch in the delta tree.
The m flag defines the first choice for the replacement
text of the %M% identification keyword. The f flag
defines the the release below which no deltas may be
added (also known as the floor release).
The c flag defines the the release above which no
deltas may be added (also known as the ceiling
release).
The d flag defines the default SID to be used when none
is specified on a get command.
The n flag causes delta to insert a null delta (a delta
that applies no changes) in those releases that are
skipped when a delta is made in a new release (e.g.,
when delta 5.1 is made after delta 2.7, releases 3 and
4 are skipped). The absence of the n flag causes
skipped releases to be completely empty.
The j flag causes get to allow concurrent edits of the
same base SID.
The l flag defines a list of releases that are locked
against editing (get(1) with the -e keyletter).
The q flag defines the replacement for the %Q%
identification keyword.
Licensed material--property of copyright holder(s) Page 3
sccsfile(4) DG/UX 4.30 sccsfile(4)
The z flag is used in certain specialized interface
programs.
Comments
Arbitrary text is surrounded by the bracketing lines @t
and @T. The comments section typically will contain a
description of the file's purpose.
Body
The body consists of text lines and control lines.
Text lines do not begin with the control character,
control lines do. There are three kinds of control
lines:
@I DDDDD Insert
@D DDDDD Delete
@E DDDDD End
The digit string is the serial number corresponding to
the delta for the control line.
SEE ALSO
admin(1), delta(1), get(1), prs(1) in the User's Reference
for the DG/UX System.
Licensed material--property of copyright holder(s) Page 4