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

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

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