1*
2* CDDL HEADER START
3*
4* The contents of this file are subject to the terms of the
5* Common Development and Distribution License (the "License").
6* You may not use this file except in compliance with the License.
7*
8* You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
9* or http://www.opensolaris.org/os/licensing.
10* See the License for the specific language governing permissions
11* and limitations under the License.
12*
13* When distributing Covered Code, include this CDDL HEADER in each
14* file and include the License file at usr/src/OPENSOLARIS.LICENSE.
15* If applicable, add the following below this CDDL HEADER, with the
16* fields enclosed by brackets "[]" replaced with your own identifying
17* information: Portions Copyright [yyyy] [name of copyright owner]
18*
19* CDDL HEADER END
20*
21* Copyright 1997 Sun Microsystems, Inc. All rights reserved.
22* Use is subject to license terms.
23*
24* Copyright 2006-2018 J. Schilling
25*
26* @(#)co	1.14 18/12/04 J. Schilling
27*
28* @(#)co 1.3 06/12/12
29*
30*#ident	"@(#)sccs:help.d/co"
31*	Messages from routines in 'com' directory of sccs.
32*
33-1
34"not an SCCS file"
35A file that you think is an SCCS file
36does not begin with the characters "s.".
37-2
38"not an sccs file"
39A file that you think is an SCCS file
40does not begin with the magic ^Ahnnnnn (SCCS v4) or ^AhV6,sum=nnnnn (SCCS v6)
41in it's first line.
42-3
43"more than one link"
44SCCS files may only have one name (link).
45This is because the delta program unlinks the old file
46and then links to the new file.
47-4
48"format error at line ..."
49The format of the SCCS file is logically invalid.  The error
50was discovered at the stated line.  See if you can find
51the problem with the prs command.  If not, do a "help stuck".
52-5
53"premature eof"
54The SCCS file ended in a strange place.  Its probably a goner.
55You can try "help stuck", but chances are you're going to
56have to go to a backup copy.
57-6
58"corrupted file"
59The computed global hash count of the input SCCS history file did not check
60with the stored hash count.  The file may have been damaged since it was
61last accessed.  See your local SCCS maintenance person.
62-7
63"too long"
64The pathname is too long.
65-8
66"invalid sid"
67The specified sid is syntactically incorrect.
68-10
69"clock set wrong!!!"
70The time of day is wrong.  Contact your local UNIX support group immediately!
71(Try a "date" command.)
72(This error is produced whenever the creation date of the newest delta
73in the SCCS file is newer than the current date.  This will happen
74whenever the date is accidently set wrong.  This error
75will also occur if a delta was created while the clock was
76set ahead - but less than a year - and has since been corrected.
77In this case the current time is correct, but the date of the
78delta is wrong.)
79-11
80"Clock may be set wrong!"
81The time of day may be set wrong.
82Check the current time with the "date" command.
83If it is wrong, contact your local UNIX support group immediately!
84(This message is produced whenever the difference between
85the current date and the creation date of the newest delta in
86the SCCS file is greater than one year.)
87-12
88"bad range"
89In a delta list, the two limits of a range of deltas were not in ascending
90order.
91-13
92"delta list syntax"
93A list of deltas was syntatically erroneous.  The correct syntax is:
94		<list>	::=  <range> | <list> , <range>
95		<range>	::=  <delta> | <delta> - <delta>
96		<delta>	::=  <rel> | <rel> . <lev>
97-14
98"not authorized to make deltas"
99Your login name or group ID is not on the list of
100users who are allowed to add deltas to this file.
101You can execute "prs -d:UN: file" to see who is allowed.
102See your project administrator to get your login name or
103group ID on the list.
104-15
105"release ... < ... (floor)"
106Either the release you specified or else the default release is lower
107than the lowest allowable release (the floor).  If you're not sure what's
108wrong see your SCCS administrator.
109-16
110"release ... > ... (ceiling)"
111Either the release you specified or else the default release is higher
112than the highest allowable release (the ceiling).  If you're not sure what's
113wrong see your SCCS administrator.
114-17
115"bad p-file format"
116The p-file is messed up.
117Get your local source code administrator to
118fix it.
119-18
120"line longer than 1024 characters"
121Don't type so much on a line.
122-19
123"response too long"
124A response can't be so long.
125Try typing less (maybe you can reference
126some other document).
127-20
128"cannot fork; try again"
129The system is busy;
130you'll have to try again later.
131-21
132"too many MRs"
133You can't enter so many MRs.
134Sorry.
135-22
136"out of space"
137Your MRs took up too much memory.
138Type less.
139-23
140... locked against editing
141The specified release (or possibly all releases) for the
142SCCS file have been locked using the _l flag of admin.  Do a
143'prs -d:LK: s.filename' to see a list of locked releases
144(_a means "all").
145-24
146"MR number too long"
147You entered an MR number which is much to long.  Remember,
148multiple MRs should be separated by spaces or tabs.
149-25
150"begins"
151An include/exclude conflict exists beginning here.  The
152SID's in the include/exclude list change conflicting lines.
153The lines involved may not be correct.
154-26
155"ends"
156An include/exclude conflict ends here.  The SID's in the
157include/exclude list change conflicting lines.  The lines
158preceding this message may be incorrect.
159-27
160"corrupted file version"
161The computed version specific hash count of the extracted file version did
162not check with the stored hash count.  The file may have been damaged
163since it was last accessed.  File version hashs are a SCCS v6 extension,
164so the problem may have been caused by an incorrect SCCS v4 -> SCCS v6
165history file conversion.  You may like to check other versions for correct
166checksums to isolate the problem.  See your local SCCS maintenance person.
167-28
168"path conversion error"
169A path could not be converted into a normalized path without
170"./" or ".." components and without symbolic links.
171-29
172"resolved path too long"
173The resolved path name is too long for further processing.
174-30
175"too many include exclude or ignore entries"
176The SCCS history file contains more a delta entry with more include,
177exclude or ignore entries than expected. Contact the SCCS maintainers
178to increase the MAXLINE constant and recompile.
179-31
180"line too long"
181A line in a file was longer than a static buffer. Contact the SCCS maintainers
182to increase the MAXLINE constant and recompile.
183-32
184"cannot get project home directory"
185The project set home directory could not be retrieved.
186The project set home is a directory that holds a directory
187".sccs" for project specific SCCS metadata. The location of this
188directory .sccs is searched for by scanning the filesystem
189towards the root directory starting from the current working
190directory. If an error occurs while trying to look for .sccs,
191a sccs program cannot find out whether the current repository
192is a project oriented SCCS v6 repository. Check and fix
193directory permissions to make sccs work again.
194-33
195"no SCCS project home directory"
196The project set home directory was not seen.
197The project set home is a directory that holds a directory
198".sccs" for project specific SCCS metadata. The location of this
199directory .sccs is searched for by scanning the filesystem
200towards the root directory starting from the current working
201directory. If the directory ".sccs" or it's default content was
202not found, SCCS cannot work in project mode.
203Try to run "sccs init" to mark a project home directory.
204-34
205"bad syntax in changeset line"
206A line in the changeset file was incorrectly structured.
207Check the changeset file for consistency. Inform your local
208SCCS administrator.
209-35
210"no initial path in data structures"
211The SCCS packet structure was not fully initialized. Inform
212your local administrator.
213-36
214"not in specified sub directory"
215The s.filename argument to admin does not contain the expected
216subdirectory as specified by -Ndir/s.
217-37
218"bad N argument"
219The argument to the 'N' keyletter contains the string 's.' but does
220not end in 's.'. Valid arguments are -Ns. or -Ndir/s.
221-38
222"not a SID-tagged filename"
223A filename argument was not in the form "+SID+filename".
224Check your input data and verify whether -N++ was intentionally specified.
225-39
226"cannot open current directory"
227Cannot open the current working directory; check permissions.
228-40
229"cannot open project home directory"
230Cannot open the project set home directory; check permissions.
231-41
232"illegal Xopt"
233X options may be specified as a comma separated list. Available options
234are listed with 'sccs help Xopts'
235