Cancels a checkout of an element
Product | Command Type |
---|---|
ClearCase | cleartool subcommand |
ClearCase LT | cleartool subcommand |
Attache | command |
Platform |
---|
UNIX |
Windows |
The uncheckout command cancels a checkout for one or more elements, deleting the checked-out version. Any metadata (for example, attributes) that you attached to a checked-out version is lost. After you cancel a checkout:
A dynamic view reverts to selecting a checked-in version of each element.
A snapshot view performs an update operation for each unchecked-out element. (For snapshot views, there is an exception for the canceling of a directory checkout; see Canceling a Directory Checkout for more information).
In Attache, if -rm is not specified, any corresponding local files are uploaded before the uncheckout command is executed remotely, so that they can be kept in the view if -keep is specified or if the keep query receives a yes answer. Local files that correspond to canceled checkouts are updated from the version selected by the view after the checkouts are canceled, and are made read-only.
The checkout version event record for each element is removed from its VOB's database. (There is no uncheckout event record.) Reserve and unreserve records are also removed.
If you checked out a file under an alternate name (checkout -out), you cannot use the alternate name to cancel the checkout-you must use the element name listed by ls -vob_only.
(ClearCase and ClearCase LT) You can cancel another dynamic view's checkout by using a view-extended pathname to the element. For a snapshot view, or in the case where a dynamic view is no longer accessible (for example, it was deleted accidentally), a view-extended pathname does not work. Instead, do the following:
Enter the command describe -long vob:pname-in-vob, where pname-in-vob is the VOB-tag of the VOB containing the checked-out file. The output of this command includes a list of views with checkouts in the VOB.
Look for the view-storage pathname of the inaccessible view, and note the view's unique identifier (UUID).
Use the uuid in the command rmview -uuid uuid to remove all of the view's checkout records from the VOB.
Repeat Step #3 in each VOB that may have been accessed with the view.
You can also change reserved checkouts in that view to unreserved. There is no way to cancel checkouts in an inaccessible view.
If you cancel a directory's checkout after changing its contents, the changes made with rmname, mv, and ln are lost. Any new elements that were created (with mkelem or mkdir) become orphaned; such elements are moved to the VOB's lost+found directory, stored under names of this form:
uncheckout displays a message in such cases:
cleartool: Warning: Object "foo.c" no longer referenced.
cleartool: Warning: Moving object to vob lost+found directory as
"foo.c.5f6815a0a2ce11cca54708006906af65".
Identities: You must have one of the following identities:
Version creator
Element owner
VOB owner
root (UNIX)
Member of the ClearCase group (ClearCase on Windows)
Local administrator of the ClearCase LT server host (ClearCase LT on Windows)
Locks: An error occurs if one or more of these objects are locked: VOB, element type, element, branch type, branch.
Mastership: (Replicated VOBs) No mastership restrictions.
HANDLING OF THE FILE. Default: For file elements only, uncheckout prompts you to decide whether to preserve a copy of the checked-out version of the element:
Save private copy of "util.c"? [yes]
A yes answer is equivalent to specifying the -keep option; a no answer is equivalent to specifying the -rm option.
SPECIFYING THE ELEMENT. Default: None.
The UNIX examples in this section are written for use in csh. If you use another shell, you may need to use different quoting and escaping conventions.
The Windows examples that include wildcards or quoting are written for use in cleartool interactive mode. If you use cleartool single-command mode, you may need to change the wildcards and quoting to make your command interpreter process the command appropriately.
In cleartool single-command mode, cmd-context represents the UNIX shell or Windows command interpreter prompt, followed by the cleartool command. In cleartool interactive mode, cmd-context represents the interactive cleartool prompt. In Attache, cmd-context represents the workspace prompt.
Cancel the checkout of file element util.c.
cmd-context uncheckout util.c
Save private copy of "util.c"? [yes] no
Checkout cancelled for "util.c".
(Dynamic views) Cancel the checkout of file hello.h in the jackson_fix view, and delete the view-private copy.
cmd-context uncheckout -rm /view/jackson_fix/usr/hw/src/hello.h
Checkout cancelled for "/view/jackson_fix/usr/hw/src/hello.h".
Cancel the checkout of directory subd after creating a new element named conv.c.
cmd-context uncheckout subd
cleartool: Warning: Object "conv.c" no longer referenced.
cleartool: Warning: Moving object to vob lost+found directory as
"conv.c.3d90000112fc11cba70e0800690605d8".
Checkout cancelled for "subd".
checkin, checkout, lscheckout, mkview, reserve, unreserve, update, attache_command_line_interface, attache_graphical_interface
Feedback on the documentation in this site? We welcome any comments!
Copyright © 2001 by Rational Software Corporation. All rights reserved. |