Tip: If you are working in a UCM environment, before setting up work
areas, consider adjusting your umask setting to control the level of access
that others have to your work.
The umask(1) setting that you have when you create a view
(in base ClearCase®)
or join a project (in a UCM environment) affects how accessible your views
will be to others. For example:
- A umask of 002 is appropriate for a view that you share
with other users in the same group. Members of your group can create and modify
view-private data; those outside your group can read view-private data, but
cannot modify it. To completely exclude users who are not group members, set
your umask to 007.
- A umask of 022 produces a view in which only you can write
data, but anyone can read data.
- A umask of 077 is appropriate for a completely private view.
No other user can read or write view-private data.
Change your umask in the standard way. For example, enter
this command from a shell:
For more information, see a umask(1) man page.
The CCASE_BLD_UMASK environment variable
You
can also use the CCASE_BLD_UMASK environment variable (EV) to set the umask(1)
value for files created from a clearmake build script.
It may be advisable to have this EV be more permissive than your standard
umask; for example, CCASE_BLD_UMASK = 2 where umask is 22.
For
more information about Rational® ClearCase environment
variables, see the env_ccase reference page.