IBM Support

PM51013: Conversion of hijack (non latest) lost after view update resulting in version content not consider/merged

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Conversion of hijack (non latest version) to checkout after view
    update checkouts incorrect version.
    
    Use Case for Reproduction:
    
    User A and user B are working on identical config specs. User A
    checkouts foo.txt/main/1, simulating development work user B
    hijacks foo.txt/main/1(inside or outside of CCRC), modifies the
    file then saves those changes. user A has modified and checked
    in foo.txt to create foo.txt/main/2. User B looks at vtree
    confirms that it shows version 1 hijacked, the user then updates
    their view(default update with hijacks kept).  The view update
    status indicates that foo.txt kept its hijack.  The user
    converts the hijack to checkout and checks in their changes,
    they are NOT presented with any merge consideration(even if it
    is trivial) of the changes that were committed by user A.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Conversion of hijack (non latest version) to checkout after
    view update checkouts incorrect version
    
    UseCase for Reproduction:
    
    user A and user B are working on identical config specs.
    User A checkouts foo.txt/main/1, simulating development work
    user B hijacks foo.txt/main/1(inside or outside of CCRC),
    modifies the file then saves those changes. user A has
    modified and checked in foo.txt to create foo.txt/main/2.
    User B looks at vtree confirms that it shows version 1
    hijacked, the user then updates their view(default update
    with hijacks kept).  The view update status indicates that
    foo.txt kept its hijack. The user converts the hijack to
    checkout and checks in their changes, they are NOT presented
    with any merge consideration (even if it is trivial) of the
    changes that were committed by user A.
    

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 number

    PM51013

  • Reported component name

    CLEARCASE WIN

  • Reported component ID

    5724G2900

  • Reported release

    712

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-10-27

  • Closed date

    2011-12-19

  • Last modified date

    2011-12-19

  • 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 WIN

  • Fixed component ID

    5724G2900

Applicable component levels

  • R712 PSN

       UP



Document information

More support for: Rational ClearCase

Software version: 7.1.2

Reference #: PM51013

Modified date: 19 December 2011