Is there a program to find out the Multi Version File System MVFS drive in Windows ?

Question

Say I've a user that copied a checked in version folder tree using ClearCase Explorer to create a view-private folder tree. Now he wants to delete it and is not allowed to delete it.

All the files and folders in the copy are owned by Nobody (S-1-1-0) and have the read-only bit set. The files could be deleted by manually going into the properties of each file and removing the read-only bit. Then the files could be deleted.

The folders are another matter. They, so far, cannot be deleted. Both as the user and as the VOB owner we've gone into the folder properties and removed the check in the read-only box and closed the properties. Reopening the properties has the read-9only check restored.

I've gone to the command prompt and used the attrib command as "attrib -r /d folder" or "attrib -r /d /s folder" or "attrib -r -a -s -h -I /d /s folder". In all cases I get "Access Denied - folder.

I've told the user that removing the view will get rid of the folders. He insists that is not possible due to other content in the view. I've suggested that they get the "other" work done and then delete the view.

So while I convince the user to just remove the view, does anyone know how to successfully delete the folder?

Answer 1

This is often the question for new trigger writers or script writers. You know it is usually the "M drive" on most installations, but you do not want to rely on the convention (and rightly so in this case) as most shops still do not "control" the desktop (in windows ClearCase is always installed locally). Your dilemma is to reliably calculate the MVFS Drive to automate some process in a script or trigger.

The first and most important thing to remember is do not assume. One may be tempted in a trigger to use the ClearCase Environmental variable CLEARCASE_PN or CLEARCASE_XPN and then grab the start of the value, which might resemble:

M:\some_view\some_vob\some_dir\foo.c

Coding to this might work for the policy maker that is accustomed to working from under the MVFS drive, but a developer might have their view mapped to some drive (i.e. "J") and they may choose to work there where the ClearCase Environmental variable CLEARCASE_PN or CLEARCASE_XPN might resemble:

J:\ some_vob\some_dir\foo.c

So something a bit more robust and reliable should be used. One option is to use the output of the net use command: