2.1 Adjusting Your umask

Your umask setting at the time you join a project affects how accessible your views are 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 nongroup 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:

umask 022

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 to set the umask value for files created from a clearmake build script. It may be advisable to have this environment variable be more permissive (that is, allow more access) than your standard umask-for example, CCASE_BLD_UMASK = 2 where umask is 22.

For more information on ClearCase environment variables, see the env_ccase reference page in the Command Reference.