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 2006-2020 J. Schilling 22* 23* @(#)cm 1.13 20/07/12 J. Schilling 24* 25* @(#)cm 1.2 06/12/12 26* 27*#ident "@(#)sccs:help.d/cm" 28* Messages common to more than one SCCS command. 29* 30-1 31"unknown key letter" 32You supplied a keyletter which the command does not recognize. 33-2 34"key letter twice" 35You supplied a keyletter more than once. 36-3 37"missing file arg" 38You left off the name of the file to be processed. 39-4 40"cannot create lock file" 41There are two known reasons why this can occur. 42 431) Someone else is updating the SCCS file (or the p-file). 44 You'll have to wait until they're through, and try again. 45 462) You do not have write permission in the directory where the 47 SCCS file resides. If this is so, you are not allowed to 48 create any files (including the ``lock file'') in that 49 directory. 50 51If it is neither of the two reasons and the problem persists, contact 52your Source Code Administrator (SCA). 53-5 54"bad date/time" 55The date/time must be a legitimate date/time in the form 56"YY[MM[DD[HH[MM[SS]]]]]". The program knows about things 57like leap years, so be precise. 58-6 59"no id keywords" 60No SCCS identification keywords were substituted for (or found). 61If this message came from delta then you just tryed to make a 62delta without any keywords. 63 64If this message came from get then 65your source code administrator blew it. 66Complain to him/her. 67 68If this message came from admin, 69you blew it. 70-7 71"No id keywords" 72No SCCS identification keywords were substituted for. 73You may not have any keywords in the file, 74in which case you can ignore this warning. 75If this message came from delta then you just made a 76delta without any keywords. 77If this message came from get then 78the last time you made a delta you changed the lines 79on which they appeared. 80It's a little late to be 81telling you that you messed up the last time you made a delta, but this is 82the best we can do for now, and it's better than nothing. 83 84If you do not like to expand keywords at all and if you do not like to get 85a warning for that case, you may like to call "admin -fy ..." 86 87This isn't an error, only a warning. 88-8 89"value after ... arg" 90You had something after the indicated keyletter argument and you weren't 91supposed to. 92-9 93"User ID not in password file ..." 94You are apparently running on a system on which you do not 95have a login (via a data link of some type). SCCS will 96not allow you to make changes to a file if your user ID is not 97located in the password file. 98-10 99"invalid id keywords" 100The specific id keywords specified to admin via -fi"string" 101were not found in the file. You are trying to delta 102a file with expanded keywords, get a file which was admin'd 103to verify keywords after the last delta, or admin a new file 104whose keywords do not match what was specified by "string". 105-11 106"cannot get project home directory" 107Outdated error code, call "sccs help co32" 108-12 109"path conversion error" 110A path could not be converted into a normalized path without 111"./" or ".." components and without symbolic links. 112-13 113"resolved path too long" 114The resolved path name is too long for further processing. 115-14 116"directory specified as s-file" 117A directory was specified as s-file when only plain files were expected. 118-15 119"file not in supported time range" 120A file uses a time stamp that is out of the supported range. 121This is most likely a result of a bad time stamp on a file. 122-16 123"cannot change directory" 124Cannot change directory while normalizing path name in project set mode. 125Check directory permissions. 126-17 127"not in tree" 128The path name is not inside the tree below the change set home directory. 129-18 130"too many file args" 131The command or operation does not support more than one argument. 132-19 133"time stamp conversion error" 134A time stamp is out of the supported range. 135This is most likely a result of a time stamp that is not supported by the 136conversion routines from the actual operating system. 137-20 138"non directory specified as argument" 139A non-directory was specified when only directories were expected. 140-21 141"input file is missing" 142A specified input file could not be found. 143-22 144"could not make directory" 145A missing directory could not be made. 146-23 147"recursive dead lock attempt" 148An attempt was made to create a lock file we did already create. 149This would cause a deadlock situation and is an implementation bug. 150 151Please report this problem. 152-24 153"parent dead lock attempt" 154An attempt was made to create a lock file that was 155already created by our parent. 156This would cause a deadlock situation and is an implementation bug. 157 158Please report this problem. 159