* @(#)26     1.3 4/25/91 19:27:40
* IBM_PROLOG_BEGIN_TAG 
* This is an automatically generated prolog. 
*  
* bos720 src/bos/usr/share/lib/sccshelp/co 1.3 
*  
* Licensed Materials - Property of IBM 
*  
* COPYRIGHT International Business Machines Corp. 1989,1991 
* All Rights Reserved 
*  
* US Government Users Restricted Rights - Use, duplication or 
* disclosure restricted by GSA ADP Schedule Contract with IBM Corp. 
*  
* IBM_PROLOG_END_TAG 
*
* COMPONENT_NAME: CMDSCCS       source code control system
*
* FUNCTIONS:
*
* ORIGINS: 27
*
* (C) COPYRIGHT International Business Machines Corp. 1989, 1991
* All Rights Reserved
* Licansed Materials - Property of IBM
*
* US Government Users Restricted Rights - Use, duplication or
* disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
*

*
*       Messages from sccs library routines.
*
-1
Specify an SCCS file with this command.
You supplied a file name that does not begin with s.

-3
SCCS files can have only one link or name.
Unlink the file, then create the SCCS file.
The delta program unlinks the old file and then links to the new file.

-4
There is a format error on the specified line.
Restore the backup copy.\
An SCCS file that is not correctly formatted could result from manual editing,
which is not a good idea, or from some sort of system error.

-5
The end of the file was premature.
Make sure that the last line of the file ends with a newline character or
use local problem reporting procedures.
The SCCS file may have been damaged by a system error or an internal error
in an SCCS command. You may need to locate a backup copy.

-6
The file is damaged.
Use local problem reporting procedures.
The computed hash count of the input SCCS file did not check with the
stored hash count.  The file may have been damaged since it was last
accessed, or it may have been manually edited.  If you think the data
is correct, run the following to correct the hash count:
admin -z

-7
The path name is too long.
You supplied an absurdly long path name.

-8
The SID you specified is not valid.
The specified SID is syntactically not correct.

-10
The creation of the newest delta in the SCCS file is later than
the current time.
Make sure that the system date is set correctly or
use local problem reporting procedures.
This message can also occur if the delta was created when the clock was not
set correctly, even though it is set correctly now, or if the delta was made
very recently at a site in a different time zone.

-11
The difference between the current date and the creation date of
the newest delta in the SCCS file is greater than 1 year.
Make sure that the system date is set correctly or
use local problem reporting procedures.

-12
The 2 limits of a delta range must be in ascending order.
In a delta list, the 2 limits of a range of deltas were not
in ascending order.

-13
The delta list syntax is not correct.
A list of deltas was syntactically erroneous.  The correct syntax is:
                <list>  ::=  <range> | <list> , <range>
                <range> ::=  <delta> | <delta> - <delta>
                <delta> ::=  <rel> | <rel> . <lev>

-14
You are not authorized to make deltas.
Use local problem reporting procedures to place your user name
or group number on the list of users who can make deltas.
To see who is allowed to add deltas, run the following:
		prs -d:UN: file

-15
The specified release is less than the lowest allowed release (the floor).
The specified release must be greater than or equal to the lowest
allowed release.
Either the release you specified or the default release is lower than the
lowest allowed release (the floor).
Use the following command to determine the current floor:
		prs -d:FB:

-16
The specified release is greater than the highest allowed release (the ceiling).
The specified release must be less than or equal to the highest allowed release.
Either the release you specified or the default release is higher than the
highest allowed release (the ceiling).
Use the following command to determine the current ceiling:
		prs -d:CB:

-17
The p-file is damaged.
Edit the p-file or restore a backup copy.
The p-file has been damaged, perhaps by manual editing.
If you do not know how to fix it, remove it and run the following command
to establish it again:
		get -e -g

-20
Cannot create another process at this time.
Try again later or
use local problem reporting procedures.
An attempt to create a subprocess failed.
You may already be running too many processes, or the system process table
may be full.

-21
too many MRs
You cannot enter so many MRs.

-23
The SCCS file is locked against editing.
The specified release is locked against editing.
The specified release (or possibly all releases) for the
SCCS file have been locked using the l flag with the admin command.
To see a list of all locked releases, run the following:
		prs -d:LK: s.file

-25
An include or exclude conflict begins at the specified line.
The SIDs in the include or exclude list change conflicting lines.
The lines involved may not be correct.

-26
An include or an exclude conflict ends at the specified line.
The SIDs in the include or exclude list change conflicting lines.
The lines preceding this message may not be correct.

-50
Cannot execute the specified program.
Check path name and permissions or
use local problem reporting procedures.
The system could not run the specified program. It may not be executable or
it may have been removed.