Unreserved elements
There are two kinds of checkouts for an element when you use ClearCase® to manage your Functional Tester test assets: reserved and unreserved.
The view with a reserved checkout has the exclusive right to check in a new version for a branch or stream. Many views can have unreserved checkouts. An unreserved checkout does not guarantee the right to create the successor version. If several views have unreserved checkouts, the first view to check in the element on a branch or stream creates the successor; developers who are working in other views must merge the checked-in changes into their own work before they can check in. Your organizational development policy may determine whether to check out reserved or unreserved.
A reserved checkout gives you the exclusive right to change that element. Only one reserved checkout is allowed on each branch of the element. Any number of unreserved checkouts are possible.
Related tasks
Add an element to source control
Related reference