Help me use MKS Integrity (source code control) more efficiently

Question

We use MKS Integrity for our source control. I have no control over that -- I just have to use it.

What are some "gotchas" that I should know about and avoid? And, are there any neat things about the software that will allow me to use it better?

I've already hit cases where the tree structure in the source control doesn't match that in my sandbox. In more than one case, a file exists in two places, and when I resynchronize, I get the current version, and then an older version overwrites it, and then it is no longer synchronized. It's a challange to find the older file, since, of course, the tree structure doesn't match.

Answer 1

Have you tried their support desk?

Answer 2

I have used Source Control since 1999. It's pretty reliable, we have never lost change history. We don't do anything fancy with branches so I can't answer your question.

I assume you did resynchronize (F6) and update to head (F7).

SI is built upon a command-line design. You might have more consistent results if you use the command-line versions (pj.exe etc). The documentation is not trivial.

We're trying to migrate to Subversion, because MKS want ridiculous money for their latest enterprisey version.