Rational ClearCase Commands Reference

SourceSafe Checked-Out Files

clearexport_ssafe issues warning messages when it encounters checked-out SourceSafe files, but still processes the files.

SourceSafe Executable in PATH

For clearexport_ssafe to work, the SourceSafe command-line executable, ss.exe, must be in your PATH environment variable. ss.exe must work without prompting you for a user name and password. To prevent prompting, you may need to use a SourceSafe user name that matches your domain login user name, or you may need to set the SSUSER environment variable and set the corresponding password to blank, or no password.

Special Characters in File Names

During import, clearimport invokes a shell to extract data from the datafile. clearimport can handle some, but not all, characters that are special to shells. The import fails for any file name that includes any of these characters:

For example:

Before running clearexport_ssafe, rename any file whose name contains these characters.

Translation File

Renaming SourceSafe labels can introduce inconsistencies over multiple runs of clearexport_ssafe. The same label may be renamed during processing of some SourceSafe files, but remain unchanged during processing of other files. You can enforce consistency by using the same translation file in multiple invocations of clearexport_ssafe. If you name such a file (using the –T option), clearexport_ssafe uses it as follows:

The first time you use clearexport_ssafe, use –T to create a new translation file. On subsequent invocations of clearexport_ssafe, use –T again and specify the same translation file, for consistent name translation.

Shares

clearexport_ssafe does not preserve shares as hard links during conversion. Instead, shares become separate elements.

Labels

clearexport_ssafe converts a SourceSafe label into a ClearCase or ClearCase LT label with the same name.

Note: Labels on SourceSafe directories are not exported.

Branches

clearexport_ssafe does not convert SourceSafe branches to ClearCase or ClearCase LT branches. Instead, clearexport_ssafe creates separate elements.

Pins

clearexport_ssafe translates SourceSafe pins to ClearCase or ClearCase LT version labels named PINNED.

No Deltas

SourceSafe lets you assign the NO DELTAS attribute to elements, which directs SourceSafe to keep only the current version of the element. SourceSafe keeps a history of all versions, but the contents of only the current version. clearexport_ssafe creates an empty version for each of the previous versions of the element and a version with contents for the current version. Because ClearCase and ClearCase LT do not include a feature comparable to NODELTAS, when you create new versions of the element, the previous versions and their contents are stored. You can, however, use the rmver –data command to remove a version's contents.

Handling of Objects That Cannot Be Exported

When clearexport_ssafe encounters a file or directory that cannot be exported (for example, a file with format problems, or a broken symbolic link), it prints an error and continues. After creating the data file, the command prints a summary of the files and directories that could not be exported.

Handling of Directory Arguments

clearexport_ssafe processes the files in your SourceSafe current project. You cannot specify a pathname with the source-name argument.

Selective Conversion of Files

Preservation of SourceSafe Information as Attributes

Creating New Versions on a Branch

Translation of Labels

Storage Location of Datafile

Note: Do not specify the OUTPUT variable in your SourceSafe initialization file (.ini).

Specifying Files to Be Exported