*
* CDDL HEADER START
*
* The contents of this file are subject to the terms of the
* Common Development and Distribution License (the "License").
* You may not use this file except in compliance with the License.
*
* You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE
* or http://www.opensolaris.org/os/licensing.
* See the License for the specific language governing permissions
* and limitations under the License.
*
* When distributing Covered Code, include this CDDL HEADER in each
* file and include the License file at usr/src/OPENSOLARIS.LICENSE.
* If applicable, add the following below this CDDL HEADER, with the
* fields enclosed by brackets "[]" replaced with your own identifying
* information: Portions Copyright [yyyy] [name of copyright owner]
*
* CDDL HEADER END
*
* Copyright 2006-2011 J. Schilling
*
* @(#)cm	1.3 11/11/08 J. Schilling
*
* @(#)cm 1.2 06/12/12
*
*#ident	"@(#)sccs:help.d/cm"
*	Messages common to more than one SCCS command.
*
-1
"unknown key letter"
You supplied a keyletter which the command does not recognize.
-2
"key letter twice"
You supplied a keyletter more than once.
-3
"missing file arg"
You left off the name of the file to be processed.
-4
"cannot create lock file"
There are two known reasons why this can occur.

1) Someone else is updating the SCCS file (or the p-file).
   You'll have to wait until they're through, and try again.

2) You do not have write permission in the directory where the
   SCCS file resides.  If this is so, you are not allowed to
   create any files (including the ``lock file'') in that
   directory.

If it is neither of the two reasons and the problem persists, contact
your Source Code Administrator (SCA).
-5
"bad date/time"
The date/time must be a legitimate date/time in the form
"YY[MM[DD[HH[MM[SS]]]]]".  The program knows about things
like leap years, so be precise.
-6
"no id keywords"
No SCCS identification keywords were substituted for (or found).
If this message came from delta then you just tryed to make a
delta without any keywords.

If this message came from get then
your source code administrator blew it.
Complain to him/her.

If this message came from admin,
you blew it.
-7
"No id keywords"
No SCCS identification keywords were substituted for.
You may not have any keywords in the file,
in which case you can ignore this warning.
If this message came from delta then you just made a
delta without any keywords.
If this message came from get then
the last time you made a delta you changed the lines
on which they appeared.
It's a little late to be
telling you that you messed up the last time you made a delta, but this is
the best we can do for now, and it's better than nothing.

This isn't an error, only a warning.
-8
"value after ... arg"
You had something after the indicated keyletter argument and you weren't
supposed to.
-9
"User ID not in password file ..."
You are apparently running on a system on which you do not
have a login (via a data link of some type).  SCCS will
not allow you to make changes to a file if your user ID is not
located in the password file.
-10
"invalid id keywords"
The specific id keywords specified to admin via -fi"string"
were not found in the file.  You are trying to delta
a file with expanded keywords, get a file which was admin'd
to verify keywords after the last delta, or admin a new file
whose keywords do not match what was specified by "string".
-11
"cannot get project home directory"
The project set home directory could not be retrieved.
The project set home is a directory that holds a directory
".sccs" for project specific SCCS metadata. The location of this
directory .sccs is searched for by scanning the filesystem
towards the root directory starting from the current working
directory. If an error occurs while trying to look for .sccs,
a sccs program cannot find out whether the current repository
is a project oriented SCCS v6 repository. Check and fix
directory permissions to make sccs work again.
-12
"path conversion error"
A path could not be converted into a normalized path without
"./" or ".." components and without symbolic links.
-13
"resolved path too long"
The resolved path name is too long for further processing.
