unreserve

Changes a reserved checkout to unreserved

APPLICABILITY

SYNOPSIS

unres·erve [ -vie·w view-storage-dir-pname ] [ -cact ]

[ -c·omment comment | -cfi·le comment-file-pname |-cq·uery | -cqe·ach | -nc·omment ]
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

Identities: You must have one of the following identities:

• Element owner

• Element group member

• 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 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 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 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.

• Change the checkout status of an element to unreserved.

cmd-context unreserve util.c

Changed checkout to unreserved for "util.c" branch "/main".

• 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

10-Aug-98.16: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

08-Dec.12:17 jackson checkout version "edge.c" from \main\1 (reserved)

cmd-context unreserve edge.c

Changed checkout to unreserved for "edge.c" branch "/main".

SEE ALSO

checkin, checkout, lscheckout, reserve, uncheckout