Version Control Systems/ClearCase ---- __Related Topics:__&nbsp; ~~[Version Control Systems/ClearCase/ConfigSpec]&nbsp;&nbsp;|&nbsp;&nbsp; [Version Control Systems/ClearCase/Branch]&nbsp;&nbsp;|&nbsp;&nbsp; ~~\\ ---- Considering the Licencing costs, pretty ordinary product. Labelling can take forever compared to other products such as CVS or Subversion. Most people aren't too comfortable with it, even people working on with it for years. Most dev shops I've worked in tend to have a dedicated ClearCase Adminsitrator or Guru everyone asks questions. Something that never really happens under CVS. ---- 1 help on cleartool commands {code}cleartool man <command_help_needed_on>{code} 1 checking the config spec of an existing view: {code}cleartool catcs{code} 1 creating a new Clearcase view snapshot view using cleartool:\\ Navigate to the directory where the view is to be copied, set the $VIEWNAME and execute:\\ {code} cleartool mkview -sna -tag "$VIEWNAME" -col -hos "`hostname`" \\ -hpa "/export/ccviews/$VIEWNAME" -gpa "/export/ccviews/$VIEWNAME" \\ "/export/ccviews/$VIEWNAME" **where `hostname` executes hostname command on that box (could use $HOSTNAME){code} Then ensure you edit the config spec: {code} cd /export/ccviews/$VIEWNAME cleartool edcs {code} 1 listing all checkout in a view using cleartool:\\ {code}cleartool lsco -me -cview -recurse{code} 1 updating a specific file using cleartool This also specifies to override and force {code}cleartool update -f -ove <file_name>{code} 2006-05-22 13:55:10.0 2005-09-16 19:57:47.0