admin(1)admin(1)NAMEadmin - create and administer SCCS files
login] ... flag[flag-val]] ... flag[flag-val]] ... mrlist] ... rel]
[name]] [comment]] file ...
login] ... flag[flag-val]] ... flag[flag-val]] ... mrlist] ... [name]]
[comment]] file ...
login] ... login] ... flag[flag-val]] ... mrlist] ... rel] [name]] file
The command is used to create new SCCS files and change the parameters
of existing ones. Arguments to which may appear in any order, ( unless
is specified as an argument, in which case all arguments after are
treated as files ) consist of option arguments, beginning with and
named files (note that SCCS file names must begin with the characters
If a named file does not exist, it is created and its parameters are
initialized according to the specified option arguments. Parameters
not initialized by an option argument are assigned a default value. If
a named file does exist, parameters corresponding to specified option
arguments are changed, and other parameters are left unaltered.
If directory is named instead of file, acts on each file in directory,
except that non-SCCS files (the last component of the path name does
not begin with and unreadable files are silently ignored. If a name of
is given, the standard input is read, and each line of the standard
input is assumed to be the name of an SCCS file to be processed.
Again, non-SCCS files and unreadable files are silently ignored.
The option arguments apply independently to all named files, whether
one file or many. In the following discussion, each option is
explained as if only one file is specified, although they affect single
or multiple files identically.
The command supports the following options and command-line arguments:
This option indicates that a new
SCCS file is to be created.
The name of a file from which the contents for a new
SCCS file is to be taken. (if name is a binary
file, then you must specify the -b option) The
contents constitutes the first delta of the file
(see the option for the delta numbering scheme).
If the option is used but the file name is omit‐
ted, the text is obtained by reading the standard
input until an end-of-file is encountered. If
this option is omitted, the SCCS file is created
with an empty initial delta. Only one SCCS file
can be created by an command on which the option
is supplied. Using a single to create two or
more SCCS files requires that they be created
empty (no option). Note that the option implies
Encode the contents of name, specified to the
option. This keyletter must be used if name is a
binary file; otherwise, a binary file will not be
handled properly by SCCS commands.
The release (rel) into which the initial delta is inserted.
This option can be used only if the option is
also used. If the option is not used, the ini‐
tial delta is inserted into release 1. The level
of the initial delta is always 1 (by default ini‐
tial deltas are named 1.1).
The name of a file from which descriptive text for
the SCCS file is to be taken. If the option is
used and is creating a new SCCS file (the and/or
options are also used), the descriptive text file
name must also be supplied. In the case of
existing SCCS files:
· A option without a file name causes removal of
descriptive text (if any) currently in the
· A option with a file name causes text (if any)
in the named file to replace the descriptive
text (if any) currently in the SCCS file.
This option specifies a
flag, and possibly a value for the flag, to be
placed in the SCCS file. Several options can be
supplied on a single command line. The allowable
flags and their values are:
Allows use of the
option on a command (see get(1)) to
create branch deltas.
The highest release (i.e., "ceiling"),
a number less than or equal to 9999,
which can be retrieved by a command for
editing. The default value for an
unspecified flag is 9999.
The lowest release
(i.e., "floor"), a number greater than
0 but less than 9999, which may be
retrieved by a command for editing.
The default value for an unspecified
flag is 1.
The default delta number
SID to be used by a command (see
Causes the message:
issued by or to be treated as a fatal
error (see delta(1)). In the absence
of this flag, the message is only a
warning. The message is issued if no
SCCS identification keywords (see
get(1)) are found in the text retrieved
or stored in the SCCS file. If a value
is supplied, the keywords must exactly
match the given string. However, the
string must contain a keyword, but must
not contain embedded newlines.
commands for editing on the same SID of
an SCCS file. This allows multiple
concurrent updates to the same version
of the SCCS file.
Only one user can perform concurrent
edits. Access by multiple users is
usually accomplished by using a common
login or a set user ID program (see
chmod(1) and exec(2)).
A list of releases to which deltas can no
longer be made. (A against one of
these locked releases fails). The list
has the following syntax:
The character in the list is equivalent
to specifying for the named SCCS file.
Omitting any list is equivalent to
Causes to create a null delta in each of those
releases being skipped (if any) when a
delta is made in a new release (such as
when making delta 5.1 after delta 2.7,
release 3 and release 4 are skipped).
These null deltas serve as so that
branch deltas can be created from them
later. The absence of this flag causes
skipped releases to be nonexistent in
the SCCS file, preventing branch deltas
from being created from them in the
User-definable text substituted for all occur‐
rences of the
keyword in SCCS file text retrieved by
The module name of the SCCS file substi‐
tuted for all occurrences of the key‐
word in SCCS file text retrieved by If
the flag is not specified, the value
assigned is the name of the SCCS file
with the leading removed.
The type of module in the SCCS file substi‐
tuted for all occurrences of keyword in
SCCS file text retrieved by
Causes to prompt for Modification Request (MR)
numbers as the reason for creating a
delta. The optional value specifies
the name of a (MR) number validity
checking program (see delta(1)). (If
this flag is set when creating an SCCS
file, the option must also be used even
if its value is null).
Causes to create files with execute permis‐
Causes removal (deletion) of the specified
flag from an SCCS file. The option can be speci‐
fied only when processing existing SCCS files.
Several options can be supplied on a single com‐
mand line. See the option for allowable flag
A list of releases to be unlocked. See the
option for a description of the flag and
the syntax of a list.
A login name, or numerical HP-UX group ID, to be
added to the list of users allowed to make deltas
(changes) to the SCCS file. A group ID is equiv‐
alent to specifying all login names common to
that group ID. Several options can be used on a
single command line. As many logins or numerical
group IDs as desired can be on the list simulta‐
neously. If the list of users is empty, anyone
can add deltas. A login or group ID preceded by
a denies permission to make deltas.
A login name or numerical group ID to be erased
from the list of users allowed to make deltas
(changes) to the SCCS file. Specifying a group
ID is equivalent to specifying all login names
common to that group ID. Several options can be
used on a single command line.
The comment text is inserted into the SCCS file as a
comment for the initial delta in a manner identi‐
cal to that of delta(1). Omission of the option
results in a default comment line being inserted
in the form:
The option is valid only if the and/or options
are specified (i.e., a new SCCS file is being
The list of Modification Request
(MR) numbers is inserted into the SCCS file as
the reason for creating the initial delta, in a
manner identical to delta(1). The flag must be
set and the (MR) numbers are validated if the
flag has a value (the name of an (MR) number val‐
idation program). Diagnostic messages occur if
the flag is not set or (MR) validation fails.
Causes to check the structure of the SCCS file (see
sccsfile(4)), and to compare a newly computed
checksum (the sum of all of the characters in the
SCCS file except those in the first line) with
the checksum that is stored in the first line of
the SCCS file. Appropriate error diagnostics are
This option inhibits writing on the file, thus
canceling the effect of any other options sup‐
plied, and therefore is only meaningful when pro‐
cessing existing files.
The SCCS file checksum is recomputed and stored
in the first line of the SCCS file (see above).
Note that use of this option on a truly corrupted
file can prevent future detection of the corrup‐
Access Control Lists (ACLs)
Do not add optional ACL entries to SCCS files. SCCS removes them, pos‐
sibly causing unexpected and undesirable access modes.
For information about the UNIX standard environment, see standards(5).
determines the interpretation of text as single- and/or multi-byte
determines the language in which messages are displayed.
If or is not specified in the environment or is set to the empty
string, the value of is used as a default for each unspecified or empty
variable. If is not specified or is set to the empty string, a default
of (see lang(5)) is used instead of If any internationalization vari‐
able contains an invalid setting, behaves as if all internationaliza‐
tion variables are set to See environ(5).
International Code Set Support
Single-byte and multi-byte character code sets are supported.
Use sccshelp(1) for explanations.
Number of lines in a SCCS file cannot exceed 99,999 lines. Each line
can be of characters in non-UNIX Standard environment and in UNIX Stan‐
dard environment (see standards(5)), including the newline.
The last component of all SCCS file names must be of the form New SCCS
files are given mode 444 (see chmod(1)). Write permission in the per‐
tinent directory is required to create a file. All writing done by is
to a temporary x-file, called (see get(1)), created with mode 444 if
the command is creating a new SCCS file, or with the same mode as the
SCCS file if it exists. After successful execution of the SCCS file is
removed (if it exists), and the x-file is renamed to the name of the
SCCS file. This ensures that changes are made to the SCCS file only if
no errors occurred.
It is recommended that directories containing SCCS files be mode 755
and that SCCS files themselves be mode 444. The mode of any given
directory allows only the owner to modify SCCS files contained in that
directory. The mode of the SCCS files prevents any modification at all
except by SCCS commands.
If it should be necessary to patch an SCCS file for any reason, the
mode can be changed to 644 by the owner, thus allowing the use of or
any other suitable editor. The edited file should be processed by an
to check for corruption followed by an to generate a proper checksum.
Another is recommended to ensure the SCCS file is valid.
also makes use of a transient lock file called which is used to prevent
simultaneous updates to the SCCS file by different users. See get(1)
for further information.
SEE ALSOdelta(1), ed(1), get(1), sccshelp(1), prs(1), what(1), sccsfile(4),