rmcomp

Removes a component

Applicability

Product

Command type

VersionVault

cleartool subcommand

VersionVault Remote Client

rcleartool subcommand

Platform

UNIX®

Linux®

Windows®

Synopsis

  • VersionVault:
    rmcomp [ –c/omment comment | –cfi/le comment-file-pname | –cq/uery
    | –cqe/ach |–nc/omment ]

    [ –f/orce ] component-selector ...

Description

The rmcomp command deletes a component object. Elements of the component and the VOB associated with the component are not deleted.

If a UCM project lists the component that you are attempting to delete, the warning Project project-name lists this component as a modified component is displayed. If you confirm the deletion (or use –force), the component is removed from the project's list of modifiable components.

Restrictions

Identities

You must have one of the following identities:

  • Component owner
  • Project VOB owner
  • root (UNIX® and Linux®)
  • Member of the VersionVault administrators group (VersionVault on Windows® only)

Locks

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

Mastership

(Replicated VOBs only) Your current replica must master the component.

Other

There cannot be any baselines of the component other than the initial baseline, and the component's initial baseline cannot be in use as a foundation baseline for a stream.

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.

Confirmation step

Default
Prompts for confirmation that the specified component is to be deleted.
–f/orce
Suppresses the confirmation step.

Specifying the component to be deleted

Default
None.
component-selector ...
Specifies one or more components to delete.

component-selector is of the form [component:]component-name[@vob-selector], where vob-selector specifies the component's project VOB.

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.

  • Remove a component that contains baselines.
    1. Issue the rmcomp command for a specified component:
      cmd-context  rmcomp parser@/usr1/tmp/foo_project 
      Remove component "parser@/usr1/tmp/foo_project"?  [no] yes
      
      cleartool: Error: Cannot remove component that has baselines other than 
      the initial baseline.
      
      cleartool: Error: Unable to remove component "parser@/usr1/tmp/foo_project".
    2. Use the lsbl command to find the baselines associated with the component:

      cmd-context lsbl –component parser@/usr1/tmp/foo_project
      2007-09-07T10:47:47  parser_INITIAL.109  bill   "parser_INITIAL"
        component: parser


      2007-09-07T10:49:06  START.109  bill   "START"
        component: parser

    3. Remove the baseline:

      cmd-context rmbl –f START.109@/usr1/tmp/foo_project
      Removed baseline "START.109@/usr1/tmp/foo_project".

    4. Reissue the rmcomp command:

      cmd-context rmcomp –f parser@/usr1/tmp/foo_project  
      Removed component "parser@/usr1/tmp/foo_project".