After clearimport finishes populating the VOB, examine the
version trees of the new elements to verify that clearexport_ssafe and
clearimport converted the Microsoft Visual SourceSafe configuration as you
expected. In HCLVersionVault
Windows Explorer or Windows Explorer, open the
folder, select an element, and view its version tree.
The following figure shows
the version tree for the mod_empl.c element from the Microsoft Visual
SourceSafe /bugfix project. Figure 1. Version tree of imported element
Branches. In the Visual SourceSafe configuration, at version 3,
the $payroll/bugfix/mod_empl.c file forms its own branch. clearexport_ssafe does
not convert Visual SourceSafe branches to HCL
VersionVault branches.
Instead, clearexport_ssafe creates separate elements. In
this case, it creates versions 1 and 2 of the mod_empl.c element
in the \progs directory, and versions 1 through 4 of mod_empl.c in
the \bugfix directory.
Version numbers. As with all elements, version 0 is created at
the root of the HCL
VersionVault version
tree.
Labels. The conversion process maps Visual SourceSafe labels directly
to HCL
VersionVault labels,
so version 2 of mod_empl.c has the REL1 label
as it does in the Visual SourceSafe configuration.
Pins. There is no feature in HCL
VersionVault equivalent to a Microsoft Visual
SourceSafe pin. Because pins sometimes perform the same function as labels, the conversion
process maps pins to labels. In the Visual SourceSafe configuration, version 3 of
mod_empl.c is pinned. The conversion process applies a label with the name
PINNED.
Shares. There is no feature in HCL
VersionVault equivalent
to a Visual SourceSafe share. clearexport_ssafe does not
preserve shares as hard links during conversion. Instead, shares become separate
elements.