Date Created: Wed 22-Sep-2010

Related Document Categories:

Get my WebSphere Application Server course here >>

Installing ClearCase 7.0.1 for Windows 2003 with Linux RedHat Interop using Atria Licensing

This document is part of a complete set-up of installing and configuring a Windows interop environment with Linux on RHEL 5. There is not another set of detailed documents anywhere on the internet out side of our site. If this article does not contain enough information, search the rest of this site: and you will find many mini articles on Linux and Windows interop and MVFS/Samba support. Also feel free to contact me if you require ClearCase consulting and support.


Technote (FAQ)

This technote explains what the IBM® Rational® ClearCase® variable CLEARCASE_PRIMARY_GROUP is used for on Microsoft® Windows® and under what circumstances it is needed.

ClearCase objects (files, directories, metadata ...) must be assigned an owner and a group at creation time.

In any given Windows environment, users are typically members of more than a single group.

If ClearCase has to create a new object, the albd server process needs to know which group should have access to that new object.

Each user has a primary group set on the Windows domain controller and by default it is set to Domain Users. ClearCase will use that primary group unless it is changed on the PDC to another group.

See technote 1125331 for more information on how the primary group impacts clients using the ClearCase Web Interface (CCWeb).
See technote 1231082 for more information on how the primary group impacts clients using the ClearCase Remote Client (CCRC).

If another group other than Domain Users is required, then the variable CLEARCASE_PRIMARY_GROUP can be set as a user environment variable for each single user.
Note: DO NOT set this variable as a system variable. It is MANDATORY to remove the CLEARCASE_PRIMARY_GROUP when set as a system environment variable as it can cause the system to crash. This environmental variable can ONLY be set it as a user environment variable.

To view or change environment variables:

Right-click My Computer, and then click Properties.
Click the Advanced tab.
Click Environment variables.
Click one the following options, for a user variable:
• Click New to add a new variable name and value.
• Click an existing variable, and then click Edit to change its name or value.
• Click an existing variable, and then click Delete to remove it.


The value of this variable is set to any group in your Windows domain to which you are a member.

The Windows 2003 Server now needs to be rebooted.

Error creating tag.
regsync:Error: Unable to open file "\\\visstore01\test_view\.view": Invalid argument

You need to add the following line to your smb..conf for Samba.

path = /viewstore01
public = yes
only guest = yes
writable = yes
printable = no

Restart Samba by using:
service smb restart

You will then need to authenticate with samba from your windows 2003 server

You should be able to see the viewstore01 samba share once you have authenticated

Once this is done, you should be ok with the view region sync

Once this is done, you should be ok with the vobregion sync

We are now going to open ClearCase Explorer

Then click right-mouse Add View shortcut

Select Dynamic from the View Type picklist then select the View Tag called test_view

Now click on the Dynamic view shortcut

Cannot start dynamic view test_view
Unable to create directory "test_view": Operation not permitted.


These are my steps to try and resolve this issue:

I logged in as vobadmin

cleartool desc -l /vobs/test_vob
View private directory "/vobs/test_vob"
Modified: Wed 22 Jul 2009 05:35:42 PM BST
User : root : r-x
Group: root : r-x
Other: : r-x


As root:

groupadd ccadm
usermod -a -G ccadm vobadmin

As vobadmin

cleartool setview test_view
cleartool mount /vobs/test_vob

cleartool protect -chown vobadmin -chmod 755 -recurse /vobs/test_vob
Changed protection on "/vobs/test_vob".
Changed protection on "/vobs/test_vob/lost+found".
Changed protection on "/vobs/test_vob/testfile.txt".


cleartool desc -l /viewstore01/test_view.vws
Non-MVFS directory "/viewstore01/test_view.vws"
Modified: Wed 22 Jul 2009 05:30:23 PM BST
User : vobadmin : rwx
Group: dev : r-x
Other: : r-x
as root:

/opt/rational/clearcase/bin/cleartool protectvob -add_group ccadm /vobstore01/test_vob.vbs

This command affects the protection on your versioned object base.
While this command is running, access to the VOB will be limited.
If you have remote pools, you will have to run this command remotely.
Pool "sdft" appears to be protected correctly.
Pool "ddft" appears to be protected correctly.
Pool "cdft" appears to be protected correctly.
Protect versioned object base "/vobstore01/test_vob.vbs"? [no] yes
Do you wish to protect the pools that appear not to need protection? [no]
VOB ownership:
owner vobadmin
group dev
Additional groups:
group ccadm



I had a problem,

Solution was to install a later version of Samba as the one with RHEL5 is not supported

, once the new version has been installed ie:

See link for RPMs

rpm -ivh samba3-3.2.13-40.el5.i386.rpm
rpm -ivh libwbclient0-3.2.13-40.el5.i386.rpm
rpm -ivh samba3-client-3.2.13-40.el5.i386.rpm

I was then able to access the view and mount the vob:

snaged the smb.conf entries from

path = /vobstore01/
guest ok = yes
; guest only = no
writeable = yes
printable = no
; browseable = yes


path = /vobstore01/
guest ok = yes
; guest only = no
writeable = yes
printable = no
; browseable = yes

restarted smb service


Full smb.conf

# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options (perhaps too
# many!) most of which are not shown in this example
# For a step to step guide on installing, configuring and using samba,
# read the Samba-HOWTO-Collection. This may be obtained from:
# Many working examples of smb.conf files can be found in the
# Samba-Guide which is generated daily and can be downloaded from:
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not made any basic syntactic errors.
#======================= Global Settings =====================================
msdfs root = No
host msdfs = No
netbios name = clearcase
# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
#workgroup = win2003.screv.local
workgroup = win2003
# server string is the equivalent of the NT Description field
server string = ClearCase Linux Server

# Security mode. Defines in which mode Samba will operate. Possible
# values are share, user, server, domain and ads. Most people will want
# user level security. See the Samba-HOWTO-Collection for details.
security = domain

# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
; hosts allow = 192.168.1. 192.168.2. 127.

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
; load printers = yes

# you may wish to override the location of the printcap file
; printcap name = /etc/printcap

# on SystemV system setting printcap name to lpstat should allow
# you to automatically obtain a printer list from the SystemV spool
# system
; printcap name = lpstat

# It should not be necessary to specify the print system type unless
# it is non-standard. Currently supported print systems include:
# bsd, cups, sysv, plp, lprng, aix, hpux, qnx
; printing = cups

# This option tells cups that the data has already been rasterized
cups options = raw

# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
; guest account = pcguest

# this tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/%m.log

# Put a capping on the size of the log files (in Kb).
max log size = 50

# Use password server option only with security = server
# The argument list may include:
# password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
;password server = *
password server = hs001.win2003.screv.local

# Use the realm option only with security = ads
# Specifies the Active Directory realm the host is part of
;realm = win2003.screv.local

# Backend to store user information in. New installations should
# use either tdbsam or ldapsam. smbpasswd is available for backwards
# compatibility. tdbsam requires no further configuration.
; passdb backend = tdbsam

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting.
# Note: Consider carefully the location in the configuration file of
# this line. The included file is read at that point.
; include = /usr/local/samba/lib/smb.conf.%m

# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
; interfaces =

# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
; local master = no

# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
; os level = 33

# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
; domain master = yes

# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
; preferred master = yes

# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations.
; domain logons = yes

# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
; logon script = %m.bat
# run a specific logon batch file per username
; logon script = %U.bat

# Where to store roving profiles (only for Win95 and WinNT)
# %L substitutes for this servers netbios name, %U is username
# You must uncomment the [Profiles] share below
; logon path = \\%L\Profiles\%U

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
; wins support = yes

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z

# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one WINS Server on the network. The default is NO.
; wins proxy = yes

# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The default is NO.
dns proxy = no

# These scripts are used on a domain controller or stand-alone
# machine to add or delete corresponding unix accounts
; add user script = /usr/sbin/useradd %u
; add group script = /usr/sbin/groupadd %g
; add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
; delete user script = /usr/sbin/userdel %u
; delete user from group script = /usr/sbin/deluser %u %g
; delete group script = /usr/sbin/groupdel %g

#============================ Share Definitions ==============================
comment = Home Directories
browseable = no
writeable = yes

# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
; comment = Network Logon Service
; path = /usr/local/samba/lib/netlogon
; guest ok = yes
; writable = no
; share modes = no

# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
; path = /usr/local/samba/profiles
; browseable = no
; guest ok = yes

# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
comment = All Printers
path = /usr/spool/samba
browseable = no
# Set public = yes to allow user 'guest account' to print
; guest ok = no
; writeable = no
printable = yes

# This one is useful for people to share files
comment = Temporary file space
path = /tmp
writeable = yes
guest ok = yes
public = yes
browseable = yes

# A publicly accessible directory, but read only, except for people in
# the "staff" group
; comment = Public Stuff
; path = /home/samba
; public = yes
; writable = yes
; printable = no
; write list = @staff

# Other examples.
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
; comment = Fred's Printer
; valid users = fred
; path = /homes/fred
; printer = freds_printer
; public = no
; writable = no
; printable = yes

# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
; comment = Fred's Service
; path = /usr/somewhere/private
; valid users = fred
; public = no
; writable = yes
; printable = no

# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %U option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
; comment = PC Directories
; path = /usr/pc/%m
; public = no
; writable = yes

# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
; path = /usr/somewhere/else/public
; public = yes
; only guest = yes
; writable = yes
; printable = no

# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
; comment = Mary's and Fred's stuff
; path = /usr/somewhere/shared
; valid users = mary fred
; public = no
; writable = yes
; printable = no
; create mask = 0765
path = /vobstore01
guest ok = yes
; guest only = no
writeable = yes
printable = no
; browseable = yes
path = /viewstore01
guest ok = yes
public = yes
only guest = no
writable = yes
printable = no

Get my WebSphere Application Server course here >>

Steve Robinson - IBM Champion 2013

About Me

Steve Robinson has been working in IT for over 20 years and has provided solutions for many large-enterprise corporate companies across the world. Steve specialises in Java and Middleware.

In January 2013, I was awarded the prestigous 'IBM Champion' accolade.

  • Linked In
  • Twitter
  • About Me
  • My Blog
  • Contact Me

Read my books?

IBM WebSphere Application Server 8.0 Administration Guide

IBM WebSphere Application Server 8.0 Administration Guide

WebSphere Application Server 7.0 Administration Guide

WebSphere Application Server 7.0 Administration Guide

WebSphere Categories

Other Categories