Bill Roper's Journal

As of last night, both of my machines that are using Remote ClearCase were messed up. One machine was refusing to find files that should have been in a view. On the other machine, the computer had hung while running a big merge and had to be restarted with the big red switch. After that, it would no longer display any of my existing views in CCRC. Nor would it let me add them back.

Our ClearCase support guy managed to figure out that the problem with the first machine was that I had mangled the view configuration for the view, which was what was causing it to fail. My boss had created a branch for me before leaving on vacation, but had mangled the typing in the view configuration script that he had sent so that it wouldn't parse. In the process of fixing that, I erroneously removed some things that were necessary. Once the support guy found the problem, that was easily fixed.

Did I mention that I have never had any ClearCase training? Or that there is no available documentation (that I have found) on how to write a view configuration script?

Meanwhile, on the other machine, we uninstalled CCRC. We reinstalled CCRC. It still didn't work. We downloaded the CCRC installer, uninstalled, and reinstalled again. Still no joy.

Sometime this evening, I managed to Google up the solution. I renamed the .ccase_wvreg file. This got the old views out of the way so that I could readd them one at a time. And the .copyarea files in the view that had been being merged when the system crashed were hosed.

I am now trying to find out if there's any way to restore the view. If not, I guess I'll just create a new one.

With a different name, because ClearCase will surely not let me reuse the old name.

*thud* *thud* *thud*

Today, I finally managed to send some delayed e-mails for ISFiC Press. I also assembled the new con-going bookshelves for the table and disposed of the old boards. I'm ready to place CD orders for Marcon, some of which I may manage to get filled next weekend at Consonance.

I also spent time fighting with ClearCase on the work machine, but that was much less productive in terms of my homework. :)

I spent several hours this afternoon trying to get ClearCase Remote Client installed and working with Visual Studio 2010. This would have gone better if we were on a more recent version of ClearCase.

Unfortunately, it didn't go at all.

*sigh*

Today, I tried merging the locking version -- which includes later changes from the current main line and two DLLs of mine that someone else thoughtfully deleted from the project and which I had to restore -- to my current working line where I'm trying to merge a bunch of changes from a three year old line where I was working on something. Unfortunately, something has gone wrong and I now have "evil twin" files for a bunch of the files that I restored to the locking version.

*thud* *thud* *thud*

Tomorrow, I'll try deleting the duplicates and see if I can keep the versions from the locking line. Maybe that will work...

I've almost got this round of the project that I'm working on ready to go. A bit of clean up work still remains, but after that I can go forward again instead of sideways.

Unfortunately, ClearCase has once again decided to distinguish itself by refusing to accept a check in for about a third of the files that I had checked out. It just silently refuses to check them in, giving no error message of any kind. Why these files are different from the ones where the check in succeeded is Yet Another ClearCase Mystery.

So I've asked for help. *sigh*