-1
"missing -r argument"
You must specify an SID when you are
listed more than once in the p-file.
-2
"not in p-file"
You're not listed in the p-file.
You probably forgot to do a get -e.
-3
"invalid sid in p-file"
Get your local source code administrator to fix
up the p-file.
-4
"diff failed"
The program delta uses to determine what changed failed, 
and the delta is not made.
Contact SCCS support personnel for further assistance.
-5
"internal error in delta/enter()"
Report this to your local SCCS support personnel immediately.
-6
"internal error in delta/enter()"
Report this to your local SCCS support personnel immediately.
-7
"internal error in delta/enter()"
Report this to your local SCCS support personnel immediately.
-8
"MRs not allowed"
You specified MRs, but the file being processed
doesn't allow them.
-9
"invalid MRs"
The MR validation program returned a non-zero
status to delta.  This indicates that one or more
of the MRs specified are invalid.
-10
"MRs required"
No MRs were specified, but the file being processed
requires them.
-11
"cannot fork, try again"
Delta could not fork to invoke the program it uses to determine
what has changed in the SCCS file.
This is a system problem which may go away, so try again.
If it doesn't, report it to the system support group.
-12
"cannot execute ..."
The named program, used by delta to determine what changed
in the SCCS file, could not be executed.
It may be unexecutable, or it may have been removed.
Contact SCCS support personnel for further assistance.
-13
"... failed, re-trying, segmentation = ..."
The named program, used by delta to determine what has changed in
the SCCS file, has failed.  The most likely cause is that the files
to be compared by the named program are being segmented into chunks
which are too large.  Therefore, delta re-tries with smaller chunks.
(However, the smallest chunk it will try is 500 lines.  If this fails,
it gives up hope and terminates processing of the SCCS file.)
