spk-logo-white-text-short2
0%
1-888-310-4540 (main) / 1-888-707-6150 (support) info@spkaa.com
Select Page

How To Use ClearCase clearfsimport and Avoid Pitfalls

Written by SPK Blog Post
Published on December 5, 2013

This week we will change things up a bit and have a look at an IBM/Rational ClearCase utility used for importing files into ClearCase source control. The utility command, clearfsimport, can be used to import any sort of file from a variety of other source control management (SCM) systems, or from a flat file system. It is this latter case that we will look at – importing files into ClearCase from a flat file system.

We have prepared a free document which gives information on the following kinds of issues:

  1. Example of how clearfsimport can be used correctly, and also examples of how unintended consequences can arise.
  2. How to run clearfsimport and view the results, without actually importing code or changing anything. Being able to preview a code import can save much time and trouble if something goes wrong because the import parameters are incorrectly specified.
  3. Tips on creating log files which record the import for later review.

This free document gives additional details and examples on using clearfsimport, and some of the pitfalls that can produce unexpected results.

Download this free document — and make sure to check back soon and let us know what you thought about this article!

Next Steps:

Latest White Papers

A Checklist for Reducing Time to Market in Engineering

A Checklist for Reducing Time to Market in Engineering

Product teams all have the same goal: produce high-quality products and reduce time to market. Achieving these goals simultaneously can be difficult, but your team doesn’t have to sacrifice one for the other. Learn how in this eBook.What You Will Learn In this eBook,...

Related Resources

The Hidden Cost of Disconnected Engineering Systems

The Hidden Cost of Disconnected Engineering Systems

Key Takeaways: Disconnected PLM, ALM, DevOps, and quality systems impose a “hidden engineering tax,” turning engineers into human middleware who search for information, reconcile conflicting records, duplicate work, and chase changes by hand. The blog quantifies it...

10 Steps to a Successful Creo Implementation

10 Steps to a Successful Creo Implementation

Key Takeaways Successful Creo implementation starts with a clear plan. Involving engineering, IT, and management early helps align technical requirements with business goals and reduces deployment challenges. Hardware readiness and standardized workflows are...

Why Traceability Is the Foundation of Modern Compliance

Why Traceability Is the Foundation of Modern Compliance

Key Takeaways End-to-end traceability is essential for regulatory compliance. Connecting requirements, risks, tests, changes, and approvals helps organizations maintain accurate compliance records throughout product development. Connected traceability improves audit...