PM04810: SCM adapter showing 'hijacked' status on symlink in dynamic view

APAR status

• Closed as Permanent restriction.

Error description

• Description of problem:
  =======================
  SCM adapter showing 'hijacked' status on symlink in dynamic view
  
  
  Environment:
  ============
  ClearCase 7.0.1.7
  SCM Adapter 7.0.0.20081031A
  Eclipse 3.4.2
  Windows XP SP3
  
  
  Steps to reproduce:
  ===================
  1. Put an Eclipse project under source control in a dynamic view
  2. From command-line, create a symbolic link in the project:
  ?cleartool ln -f -nco -slink target.c symlink
  ?cleartool ls
  target.c@@\main\1 Rule: \main\LATEST
  symlink --? target.c
  
  3. Checkout target.c
  4. From Eclipse IDE, right-click on the symlink and select Team
  =? 'Undo Hijack' option is available !
  
  5. If you now select 'Undo Hijack', target.c becomes read-only
  6. You have to unco/co target.c to be able to edit it
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  vob symlink artifact shows "hijacked" status in dynamic
  view.
  

Problem conclusion

• The workaround is to open the property sheet on the errant
  artifact and clear the readonly flag.  As hijacks are not
  possible in a dynamic view, one should never need to do an
  "undo hijack"  Since CC does not do directory notification
  in a dynamic view, use of the MVFS refresh adapter and
  enabling auto workspace refresh will show correct status of
  the artifact. However since SCC does not deal well with
  symlinks, CM operations such as checkout/checkin will not
  work on the symlink.  Increased type/status checking
  unfortunately have significant performance implications so
  "fixing" this beyond what is discussed here is not really
  feasible.
  

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

Applicable component levels