unreserve
Changes a reserved checkout to unreserved
Applicability
Product |
Command Type |
|---|---|
ClearCase® |
cleartool subcommand |
|
ClearCase Remote Client |
rcleartool subcommand |
Platform |
|---|
UNIX |
|
Linux |
Windows |
Synopsis
- ClearCase:
- unres/erve [ –vie/w view-storage-dir-pname ] [ –cact ]
- [ –c/omment
comment | –cfi/le
comment-file-pname |–cq/uery | –cqe/ach
| –nc/omment ] pname ...
- ClearCase Remote Client:
- unres/erve [ –cact ] pname ...
Description
The unreserve command changes the checkout status of a checked-out version of an element to unreserved. A temporary unreserve 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 ClearCase administrators group (ClearCase 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) No mastership restrictions.
Options and arguments
Specifying the view
- Default
- The current view's checkout is changed (unless you specify an element with a view-extended pathname).
- –vie/w view-storage-dir-pname
- Specifies the view whose checkout is to be changed. For view-storage-dir-pname, use the view storage directory pathname listed by the lscheckout –long command. (On UNIX and Linux systems, the host: prefix is optional.)
Event records and comments
- Default
- Creates one or more event records, with commenting controlled by your .clearcase_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
- (UCM) Unreserves 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 might 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 might 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 unreserved.
cmd-context unreserve util.c
Changed checkout to unreserved for "util.c" branch "/main". - On a Windows system, change the checkout status of an element
in another view to unreserved. Note that the view's storage area is on a remote host.
cmd-context lscheckout –long hello.c 2006-08-10T16:59:25 Ellie Jackson (jackson.user@oxygen) checkout version "hello.c" from \main\37 (reserved) by view: jackson_fix ("oxygen:C:\users\jackson\ccviews\fix.vws") "merge from bugfix branch" cmd-context unreserve –view oxygen:C:\users\jackson\ccviews\fix.vws hello.c Changed checkout to unreserved for "hello.c" branch \main". - Check out an element, check
its status, and change its status to unreserved.
cmd-context co –nc edge.c
Checked out "edge.c" from version "/main/1".
cmd-context lscheckout edge.c
—12-08T12:17 jackson checkout version "edge.c" from /main/1 (reserved)
cmd-context unreserve edge.c
Changed checkout to unreserved for "edge.c" branch "/main".