chactivity

Changes an activity

APPLICABILITY

SYNOPSIS

chact·ivity [ -c·omment comment | -cfi·le pname | -cq·uery | -cqe·ach | -nc·omment ]

{ [ -hea·dline headline activity-selector ... ] |
  [ -fcs·et src-activity-selector -tcs·et dest-activity-selector version-pname[,...] }

DESCRIPTION

The chactivity command modifies one or more activities. Use this command for these tasks:

• Changing an activity's headline

• Moving versions from the change set of one activity to the change set of another activity

Note that changing the headline for an activity does not affect its name (its unique identifier). For information about changing the activity's name, see rename.

The destination activity must exist before you can move a change set and both the source and destination activities must be in the same stream. Use lsactivity -long to list the pathnames of change-set versions associated with an activity.

RESTRICTIONS

Identities: No special identity required.

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

Mastership: (Replicated VOBs only) Your current replica must master the activity.

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

MODIFY AN ACTIVITY'S HEADLINE. Default: None.

-hea·dline headline

Specifies a new headline for the activity. The headline argument can be a character string of any length. Use double quotes to enclose a headline with spaces or special characters.

SPECIFYING THE ACTIVITY.  Default: None.

activity-selector ...

Specifies one or more activities to modify.

You can specify an activity as a simple name or as an object selector of the form [activity]:name@vob-selector, where vob-selector specifies a project VOB (see the cleartool reference page). If you specify a simple name and the current directory is not a project VOB, then this command assumes the activity resides in the project VOB associated with the stream attached to the current view. If the current directory is a project VOB, then that project VOB is the context for identifying the activity.

SPECIFYING THE SOURCE AND DESTINATION ACTIVITIES.  Default: None.

-fcs·et src-activity-selector

Specifies the activity from which to move versions.

You can specify an activity as a simple name or as an object selector of the form [activity]:name@vob-selector, where vob-selector specifies a project VOB (see the cleartool reference page). If you specify a simple name and the current directory is not a project VOB, then this command assumes the activity resides in the project VOB associated with the stream attached to the current view. If the current directory is a project VOB, then that project VOB is the context for identifying the activity.

-tcs·et dest-activity-selector

Specifies the activity to move versions to. These versions are recorded in the activity's change set.

You can specify an activity as a simple name or as an object selector of the form [activity]:name@vob-selector, where vob-selector specifies a project VOB (see the cleartool reference page). If you specify a simple name and the current directory is not a project VOB, then this command assumes the activity resides in the project VOB associated with the stream attached to the current view. If the current directory is a project VOB, then that project VOB is the context for identifying the activity.

version-pname[,...]

One or more version-extended pathnames that specify the versions to be moved to another change set.

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.

NOTE: In the UNIX examples that follow, arguments and output that show multicomponent VOB tags are not applicable to ClearCase LT, which recognizes only single-component VOB tags. In this manual, a multicomponent VOB tag is by convention a two-component VOB tag of the form /vobs/vob-tag-leaf-for example, /vobs/src. A single-component VOB tag consists of a leaf only-for example, /src. In all other respects, the examples are valid for ClearCase LT.

• Change an activity's headline.

cmd-context chactivity -headline "Fix front matter" fix_copyright
Changed activity "fix_copyright".

• Move a version from one activity's change set to another activity's change set.

cmd-context chactivity -fcset update_date \
-tcsets fix_copyright add_proc@@/main/chris_webo_dev/1

Moved version "add_proc@@/main/chris_webo_dev/1" from activity "update_date" to activity "fix_copyright".

SEE ALSO

lsactivity, mkactivity, rename, rmactivity