IBM Support

PM42270: CHBL/MKBL FAILS TO REPORT REASON WHEN INCREMENTAL LABELLING FAILS

Subscribe

You can track all active APARs for this component.

 

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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 June 2012