setactivity

Specifies the current UCM activity for your view

APPLICABILITY

ClearCase UCM (cleartool subcommand)

SYNOPSIS

setact·ivity [ -c·omment comment | -cfi·le pname | -cq·uery | -nc·omment ]

[ -vie·w view-tag ] { -none | activity-selector }

DESCRIPTION

The setactivity command sets or unsets a current activity for a view. The current activity is one whose change set records your current work. Each view can have no more than one current activity. When you check out an element, it is associated with the current activity.

By default, the setactivity command works with your current view. You can select another view/stream combination with the -view option. The view must be attached to the specified activity's stream.

Before resetting to another activity, the setactivity command checks on whether any elements of the current activity are checked out in the view and, if found, issues a warning before proceeding.

You can set an activity for a view while the activity is being delivered, but the changes made to the activity when the deliver operation is in progress are not delivered. To clear the current activity, specify a new activity or use the -none option.

You cannot reset an integration activity that is in use as part of a deliver or rebase operation (nor can you clear it with -none).

Behavior for ClearQuest-enabled projects

When executed in a view that is associated with a ClearQuest-enabled project, this command takes an activity-selector that is a ClearQuest record-ID (for example, SAMPL123456) of an existing ClearQuest record. If the ClearQuest record is not already linked to an activity, the command causes an activity to be created and linked to the ClearQuest record.

When you have finished working on an activity

You can stop work on an activity in these ways:

• Deliver the activity to the project's integration stream.
• Issue another setactivity command, specifying a different activity selector
• Use the -none option to unset the current activity in your view.

PERMISSIONS AND LOCKS

Permissions Checking: None.

Locks: An error occurs if there are locks on the following objects: UCM project VOB or the activity.

Mastership: The activity must be locally mastered.

OPTIONS AND ARGUMENTS

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.

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

CHOOSING A WORK AREA. Default: Current view context.

-vie·w view-tag

Specifies a view and stream context for the command.

SELECTING OR DE-SELECTING AN ACTIVITY. Default: None.

-none

Unsets the current activity, removing it from your work area.

activity-selector

Identifies the activity to be set.

activity-selector is of the form: [activity:]activity-name[@vob-selector] and vob is the activity's UCM project VOB.

EXAMPLES

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.

• Unset the current activity.

cmd-context setactivity -none

Cleared current activity from view java_int.

• Set an activity to be the current activity.

cmd-context setactivity activity990917.133255@\vobs\core_projects
Set activity "activity990917.133255" in view "java_int".

SEE ALSO

chactivity, lsactivity, mkactivity, rmactivity