5.4 ClearCase Access Control on UNIX and Windowscontents@cc_inter.hlp">

This section presents the differences between the UNIX and Windows implementations of ClearCase security features. For more information on ClearCase access control, see Chapter 3, Understanding ClearCase Access Controls.

• View protection mode-A Windows view always has read, write, and execute permission for the view's owner and group, and it has read and execute permission for others. On UNIX, a view's protection mode is determined by the umask of the view's creator.

• View-private file protection mode-In a Windows dynamic view, view-private files (including checked-out files) initially have read, write, and execute permission for all users. You can later specify whether all users have write permission, but you cannot change any other permissions. On UNIX, a view-private file's initial protection mode is determined by the umask of the file's creator, and you can change it later.

• Reporting protection modes for elements-On Windows, you cannot use standard operating system commands to view ClearCase protection modes for elements. Instead, in Windows Explorer, click ClearCase > Properties of Element on an element's shortcut menu, and then click the Protection tab.

• Adding executable files to source control-When you add an executable file to source control on Windows, ClearCase makes the file read-only by setting its protection to 0444. To make the file executable, run the following command:

cleartool protect -chmod +x filename

Alternately, from Windows Explorer, select the executable, and click ClearCase > Properties of Element on the shortcut menu. On the Protection tab, select Execute under Owner, Group, or Other, as appropriate.