Converts an unreserved checkout to reserved
ClearCase (cleartool subcommand), Attache (command)
The reserve command changes the checkout status of a checked-out version of an element to reserved. A temporary reserve checkout of version event record is written to the VOB database.
Permissions Checking: For each object processed, you must be one of the following: element group member, element owner, VOB owner, member of the ClearCase group. See the permissions reference page.
Locks: An error occurs if any of the following objects are locked: VOB, element type, element, branch type, branch.
Other restrictions: The following conditions must all be true:
EVENT RECORDS AND COMMENTS. Default: Creates one or more event records, with commenting controlled by your .clearcase_profile file (default: -nc). See CUSTOMIZING COMMENT HANDLING in the comments reference page. Comments can be edited with chevent.
SPECIFYING THE ELEMENTS. Default: None.
Examples including 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 command interpreter prompt. In cleartool interactive mode, cmd-context represents the interactive cleartool prompt. In Attache, cmd-context represents the workspace prompt.
cmd-context reserve util.c
Changed checkout to reserved for "util.c" branch "\main".
cmd-context lscheckout util.c
14 Mar.13:48 drp checkout version "util.c" from \main\3 (unreserved)
"experiment with algorithm for returning time"
cmd-context reserve util.c
Changed checkout to reserved for "util.c" branch "\main".
checkin, checkout, lscheckout, uncheckout, unreserve
|
Feedback on the documentation in this site? We welcome any comments!
Copyright © 1999 by Rational Software Corporation. All rights reserved. |