ClearCase permission control is based on Domain groups. If the job role's groups is over 32 groups, ClearCase creds command could not read the left groups. The issue is really bothering our customer and they always complain our products. Especially, the compains are always from their BOSS( such as project manager) who is belong to many groups and want to see all of the assets in different VOBs. Here is some work aroud to hope you treat the problem if you are facing the complain from your customer.
1. Make use of the CLEARCASE_GROUPS environment variable
Set appropriate CLEARCASE_GROUPS variable in Control Panel
Logout
Login
If you customer is the method is not convenient for them, you can create evn bat file for them and put the bat file on developer desktop. The bat file is something like:
set CLEARCASE_GROUPS ="g1,g2,¡K.g32" ----------- for env1.bat
set CLEARCASE_GROUPS ="g33, g34¡K., g64" ---------for env2.bat
2. Make use of additional users
Ask domain controller administrator to setup additional users Each user belongs to different 32 groups When the developer or PM want to see a VOB belongs to a particular group
Simply use Windows' "runas" command to launch ClearCase Explorer
For example,
runas /user:domain\user1 ccexplorer.exe
We can create shortcuts for this
Shortcut for runas /user:domain\user1 ccexplorer.exe
Shortcut for runas /user:domain\user2 ccexplorer.exe
Shortcut for runas /user:domain\user3 ccexplorer.exe
The disadvantage of this is that additional license will be consumed
3. Share the snapshot views
Ask each group to share their snapshot views. Make share only accessible to the boss
The boss can access those snapshot views via normal Windows network share
Advantage of this is that no license is consumed.
We can create batch files for this
Batch file should look something like
net use z: /d
net use z: \\host1\share1
