Fixes are available
Rational ClearCase Fix Pack 07 (7.1.2.7) for 7.1.2
Rational ClearCase Fix Pack 03 (8.0.0.3) for 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
When a full labeled baseline labels multiple versions of the same element (an invalid situation) then making a new baseline with this as 'backstop' fails with the messages: ?chbl ... Begin incrementally labeling baseline 'LABEL_Integration_110617'. (cleartool: Warning: Possible stranded temporary lbtype name found: 'LABEL_Integration_110617_in_progress'.) cleartool: Error: Error incrementally labeling baseline 'LABEL_Integration_110617'. cleartool: Error: Some baselines could not be labeled. It SHOULD fail with: ?chbl ... Begin incrementally labeling baseline 'LABEL_Integration_110617'. (cleartool: Warning: Possible stranded temporary lbtype name found: 'LABEL_Integration_110617_in_progress'.) cleartool: Error: More than one version with label of type 'LABEL_Integration_110617'. cleartool: Error: Error incrementally labeling baseline 'LABEL_Integration_110617'. cleartool: Error: Some baselines could not be labeled. Steps to Reproduce: NOTE: This situation could arise only as a result of some other defect, or by following the following steps to emulate such a defect. Put a predecessor baseline label on two versions of an element to be labeled. ?cleartool mklbtype -replace -pbranch LABEL_Integration_110616@\CVOB ?cleartool mklabel -nc LABEL_Integration_110616_Docs \CVOB\Docs\foo.doc@@\main\0 ?cleartool mkbl -component Docs@\PVOB Workaround: N/A Workaround of actually having the 'ambiguously labeled element' situation is to identify the element and remove the label from one of the versions. To do this the folowing commands are useful: cleartool find -all -version 'lbtype(PRED_FULL_LABEL)' -print ? find-version.log cleartool find -all -element 'lbtype_sub(PRED_FULL_LABEL)' -print ? find-element.log
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * **************************************************************** * PROBLEM DESCRIPTION: * **************************************************************** * RECOMMENDATION: * **************************************************************** Problem Description: =============== When a full labeled baseline labels multiple versions of the same element (an invalid situation) then making a new baseline with this as "backstop" fails with the messages: ?chbl ... Begin incrementally labeling baseline "LABEL_Integration_110617". (cleartool: Warning: Possible stranded temporary lbtype name found: "LABEL_Integration_110617_in_progress".) cleartool: Error: Error incrementally labeling baseline "LABEL_Integration_110617". cleartool: Error: Some baselines could not be labeled. It SHOULD fail with: ?chbl ... Begin incrementally labeling baseline "LABEL_Integration_110617". (cleartool: Warning: Possible stranded temporary lbtype name found: "LABEL_Integration_110617_in_progress".) cleartool: Error: More than one version with label of type "LABEL_Integration_110617". cleartool: Error: Error incrementally labeling baseline "LABEL_Integration_110617". cleartool: Error: Some baselines could not be labeled. Solution Description: ============= There were some unnecessary checks being performed to print the message. Removed the unnecessary check and the message gets printed now.
Problem conclusion
A fix is available in ClearCase versions 7.1.2.7 and 8.0.0.3
Temporary fix
Comments
APAR Information
APAR number
PM42270
Reported component name
CLEARCASE UNIX
Reported component ID
5724G2901
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-06-23
Closed date
2012-06-25
Last modified date
2012-06-25
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
R700 PSN
UP
Document Information
Modified date:
25 June 2012