IBM Support

PM68896: Error during mklabel: cleartool: Error: Version label of type 'Label_name' already on element if branch is locked with -nuser

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When you perform a cleartool mklabel operation, you may receive
    the following error ?cleartool: Error: Version label of type
    'Label_name' already on element, under the following conditions
    
    1) There is a locked branch with an ?nuser list and the user is
    not on the list
    2) The files on  locked branch are  visible in your config spec
    3) The parent directory and/or vob root is on a branch that is
    unlocked.
    
    For example, the root of the vob and the parent folder are on
    the main branch.  There are files in the parent folder that are
    on diffeent branches:
    
    Y:\test_label?ct ls
    Folder1@@\main\1                                         Rule:
    \main\LATEST
    lost+found@@\main\0                                      Rule:
    \main\LATEST
    
    
    Y:\test_label\Folder1?ct ls
    t1.txt@@\main\br1\1                                      Rule:
    ...\br1\LATEST
    t2.txt@@\main\br2\1                                      Rule:
    ...\br2\LATEST
    t3.txt@@\main\br3\1                                      Rule:
    ...\br3\LATEST
    
    The branch ?br1? is locked with the ?nuser list.  The config
    spec makes all files visible:
    element * CHECKEDOUT
    element * .../br3/LATEST
    element * .../br2/LATEST
    element * .../br1/LATEST
    element * /main/LATEST
    
    If you are a user who is not on the ?nuser list, when you run
    the command mklabel ?recurse, you will see the following:
    
    Y:\test_label?ct mklabel -recurse LB1 .
    Automatically created label type 'LB1' from global definition in
    VOB '\Admin_vob'.
    cleartool: Error: Lock on global branch type 'br1' (in VOB
    \Admin_vob) prevents operation 'make label'.
    cleartool: Error: Object locked except for users: sue_test.
    cleartool: Error: Trouble applying label to '.\Folder1\t1.txt'.
    cleartool: Error: Version label of type 'LB1' already on
    element.
    cleartool: Error: Trouble applying label to '.'.
    cleartool: Error: Version label of type 'LB1' already on
    element.
    cleartool: Error: Trouble applying label to '.\Folder1'.
    cleartool: Error: Unable to create label 'LB1' on '.' version
    '\main\1'.
    cleartool: Error: Unable to create label 'LB1' on '.\Folder1'
    version '\main\1'.
    cleartool: Error: Unable to create label 'LB1' on
    '.\Folder1\t1.txt' version '\main\br1\1'.
    Created label 'LB1' on '.\Folder1\t2.txt' version '\main\br2\1'.
    
    Created label 'LB1' on '.\Folder1\t3.txt' version '\main\br3\1'.
    
    Created label 'LB1' on '.\lost+found' version '\main\0'.
    Attempted to apply labels to 6 versions.
            3 newly applied
            0 moved
            0 already in place
            3 failed
    
    What you cannot see in the above message is that the root
    directory and the parent folder were labeled correctly.  You
    only receive an error message as the folders are being
    incorrectly evailuated again for the mklabel operation.
    
    WORKAROUND:
    
    Modify the config spec so the elements on the locked branch are
    not visible.  For example, comment out the line that contains
    the locked branch:
    
    element * CHECKEDOUT
    element * .../br3/LATEST
    element * .../br2/LATEST
    #element * .../br1/LATEST
    element * /main/LATEST
    
    The mklabel ?recurse operation proceeds as expected:
    
    Y:\test_label?ct mklabel -recurse LB2 .
    Automatically created label type 'LB2' from global definition in
    VOB '\Admin_vob'.
    Created label 'LB2' on '.' version '\main\1'.
    Created label 'LB2' on '.\Folder1' version '\main\1'.
    Created label 'LB2' on '.\Folder1\t1.txt' version '\main\1'.
    Created label 'LB2' on '.\Folder1\t2.txt' version '\main\br2\1'.
    
    Created label 'LB2' on '.\Folder1\t3.txt' version '\main\br3\1'.
    
    Created label 'LB2' on '.\lost+found' version '\main\0'.
    Attempted to apply labels to 6 versions.
            6 newly applied
            0 moved
            0 already in place
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Processing of a cleartool mklabel may encounter a locked
    branch, and in some cases an error is incorrectly reported.
    

Problem conclusion

  • A fix is available in ClearCase 7.1.2.9 and 8.0.0.5.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM68896

  • Reported component name

    CLRCASE MSITE W

  • Reported component ID

    5724G3200

  • Reported release

    712

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-07-13

  • Closed date

    2012-12-15

  • Last modified date

    2012-12-15

  • 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

    CLRCASE MSITE W

  • Fixed component ID

    5724G3200

Applicable component levels

  • R712 PSN

       UP



Document information

More support for: Rational ClearCase MultiSite

Software version: 7.1.2

Reference #: PM68896

Modified date: 15 December 2012