PM34898: RCLEARTOOL RMNAME -FORCE DOES NOT REMOVE AN ELEMENT THAT HAS CHECKOUTS

Rational ClearCase Fix Pack (7.1.2.5) for version 7.1.2
Rational ClearCase Fix Pack (8.0.0.1) for version 8.0
Rational ClearCase Fix Pack 14 (7.1.2.14) for 7.1.2
Rational ClearCase Fix Pack 11 (8.0.0.11) for 8.0
Rational ClearCase Fix Pack 12 (8.0.0.12) for 8.0
Rational ClearCase Fix Pack 15 (7.1.2.15) for 7.1.2
Rational ClearCase Fix Pack 13 (8.0.0.13) for 8.0
Rational ClearCase Fix Pack 16 (7.1.2.16) for 7.1.2
Rational ClearCase Fix Pack 17 (7.1.2.17) for 7.1.2
Rational ClearCase Fix Pack 14 (8.0.0.14) for 8.0
Rational ClearCase Fix Pack 18 (7.1.2.18) for 7.1.2
Rational ClearCase Fix Pack 15 (8.0.0.15) for 8.0
Rational ClearCase Fix Pack 19 (7.1.2.19) for 7.1.2
Rational ClearCase Fix Pack 16 (8.0.0.16) for 8.0
Rational ClearCase Fix Pack 17 (8.0.0.17) for 8.0
Rational ClearCase Fix Pack 18 (8.0.0.18) for 8.0
Rational ClearCase Fix Pack 19 (8.0.0.19) for 8.0
Rational ClearCase Fix Pack 20 (8.0.0.20) for 8.0
Rational ClearCase Fix Pack 21 (8.0.0.21) for 8.0

APAR status

• Closed as program error.

Error description

• Headline:
  rcleartool rmname -force does not remove an element that has
  checkouts
  
  
  APAR Description:
  
  The IBM Rational ClearCase Remote Client Command Line Interface
  (CCRC CLI) ignores the -force option of the rmname command.
  This option is intended to force the removal of the name when
  there is at least one checkout of the element.
  
  When using rmname in CCRC CLI, if there is a checkout of the
  targeted element on any version or branch, the following error
  will be seen with or without the -force option:
  
  rcleartool? rmname -nc -force f1.txt
  CRVAP0087E CCRC command 'rmname' failed: Unable to remove name
  of 'C:\ccweb\UserName\View\MyVOB\d1\f1.txt'
  Problems performing rmname.
  ClearCase CM Server: Error: Element
  'C:\ccweb\UserName\View\MyVOB\d1\f1.txt' has checkouts.
  
  This issue impacts only CCRC CLI; the rmname -force option
  functions as designed in the ClearCase full client command line
  interface.
  
  
  Steps to Reproduce the issue:
  
  1. Create a file (f1.txt) that is on two branches: branch_one
  and branch_two
  
  2. Checkout f1.txt on branch_two
  
  3. In a view whose config spec is configured to use branch_one,
  checkout the parent directory of f1.txt
  
  4. Attempt to rmname -force f1.txt using CCRC CLI
    ? rcleartool rmname -nc -force f1.txt
  
  
  WORKAROUND:
  
  - Cancel any existing checkouts of the element before performing
  an rmname from the CCRC CLI.
  
  - Perform the rmname -force operation from a ClearCase full
  client command line interface.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Headline:
  rcleartool rmname -force does not remove an element that has
  checkouts
  
  
  APAR Description:
  
  The IBM Rational ClearCase Remote Client Command Line
  Interface (CCRC CLI) ignores the -force option of the rmname
  command.  This option is intended to force the removal of
  the name when there is at least one checkout of the element.
  
  When using rmname in CCRC CLI, if there is a checkout of the
  targeted element on any version or branch, the following
  error will be seen with or without the -force option:
  
  rcleartool? rmname -nc -force f1.txt
  CRVAP0087E CCRC command 'rmname' failed: Unable to remove
  name of "C:\ccweb\UserName\View\MyVOB\d1\f1.txt"
  Problems performing rmname.
  ClearCase CM Server: Error: Element
  "C:\ccweb\UserName\View\MyVOB\d1\f1.txt" has checkouts.
  
  This issue impacts only CCRC CLI; the rmname -force option
  functions as designed in the ClearCase full client command
  line interface.
  
  
  Steps to Reproduce the issue:
  
  1. Create a file (f1.txt) that is on two branches:
  branch_one and branch_two
  
  2. Checkout f1.txt on branch_two
  
  3. In a view whose config spec is configured to use
  branch_one, checkout the parent directory of f1.txt
  
  4. Attempt to rmname -force f1.txt using CCRC CLI
    ? rcleartool rmname -nc -force f1.txt
  
  
  WORKAROUND:
  
  - Cancel any existing checkouts of the element before
  performing an rmname from the CCRC CLI.
  
  - Perform the rmname -force operation from a ClearCase full
  client command line interface.
  

Problem conclusion

• A fix is available in ClearCase versions 7.1.1.8, 7.1.2.5
  and 8.0.0.1
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  CLEARCASE UNIX

• Fixed component ID

  5724G2901

Applicable component levels

• R711 PSN

     UP