reserve
Converts an unreserved checkout to reserved
Applicability
Product |
Command type |
---|---|
VersionVault |
cleartool subcommand |
VersionVault Remote Client |
rcleartool subcommand |
Platform |
---|
UNIX® |
Linux® |
Windows® |
Synopsis
- VersionVault:
- res/erve [ –c/omment comment | –cfi/le comment-file-pname
- | –cq/uery| –cqe/ach | –nc/omment ] [ –cact ] pname ...
-
VersionVault Remote Client:
- res/erve [ –cact ] pname ...
Description
The reserve command changes the checkout status of a checked-out version of an element from unreserved to reserved. A temporary reserve checkout of version event record is written to the VOB database.
Restrictions
ACL authorization
- read-info on VOB object
- mod-checkout on the element
Non-ACL authorization
You must have one of the following identities:
- Element owner
- Element group member
- VOB owner
- root (UNIX® and Linux®)
- Member of the VersionVault administrators group (VersionVault 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 only) Your current replica must master the branch.
Other
There must be no reserved checkouts of the branch.
Options and arguments
Event records and comments
- Default
- Creates one or more event records, with commenting controlled by your .versionvault_profile file (default: –nc). See the comments reference page. Comments can be edited with chevent.
- –c/omment comment | –cfi/le comment-file-pname |–cq/uery | –cqe/ach | –nc/omment
- Overrides the default with the option you specify. See the comments reference page.
Specifying the elements
- Default
- None.
- –cact
- Reserves each checked-out version in the change set of the current activity in your view.
- pname ...
- One or more pathnames, each of which specifies an element. The checkout in the current view is changed, unless you use a view-extended pathname to specify another view.
Examples
The UNIX system and Linux 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 system and Linux shells or Windows command interpreter prompt, followed by the cleartool command. In cleartool interactive mode, cmd-context represents the interactive cleartool prompt.
- Change the checkout status of
an element to reserved.
cmd-context reserve util.c
Changed checkout to reserved for "util.c" branch "/main". - Verify that you are the only user
with a checkout of a certain file, and then convert your checkout
from unreserved to reserved.
cmd-context lscheckout util.c
—03-14T13: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".