In a dynamic view, the initial owner, group, and protection mode for a view-private file are determined differently on Linux® and on the UNIX® system than they are on Windows®.
You can use the cleartool describe command or the Linux and UNIX system-based ls command to display the owner, group, and protection mode for a view-private file or directory. You can use the Linux and UNIX system-based chown command to change the owner, the chgrp command to change the group, and the Linux and UNIX system-based chmod command to change the protection mode.
You can use the cleartool describe command or the Properties of File or Properties of Directory window in Rational ClearCase Explorer or Windows Explorer to display the owner, group, and protection mode for a view-private file or directory.
You cannot change the owner or group of a view-private file or directory. You can use the Read-only check box in Windows Explorer Properties window or the attrib +R (equivalent to mode 777) and attrib –R (equivalent to mode 555) commands to specify whether all users have write permission. You cannot change any other permissions.
A process must have write permission for both the view and a containing directory in the view to create a file or directory in the containing directory. For view permissions, see Permission to write views.
If the containing directory is an element version, the process must have write permission for the element. See Permission to write elements. If the containing directory is a view-private directory, the process must have write permission for the view-private directory. See Permission to write view-private files.
A process must have write permission for both the view and a containing directory in the view to delete a file or directory in the containing directory. For view permissions, see Permission to write views.
If the containing directory is an element version, the process must have write permission for the element. See Permission to write elements. If the containing directory is a view-private directory, the process must have write permission for the view-private directory. See Permission to write view-private files.
A process must have read permission for both the view and a view-private file or directory in the view to read the file or directory. For view permissions, see Permission to write views.
The algorithm used by Rational ClearCase considers the process’s user and group and the view-private file or directory’s owner, group, and protection mode to determine whether to grant read permission for the file or directory. See Access algorithm for VOB and view data.
A process must have write permission for both the view and a view-private file or directory in the view to write the file or directory. For view permissions, see Permission to write views.
The algorithm used by Rational ClearCase considers the process’s user and group and the view-private file or directory’s owner, group, and protection mode to determine whether to grant write permission for the file or directory. See Access algorithm for VOB and view data.
A process must have execute permission for both the view and a view-private file or directory in the view to execute the file or directory. For view permissions, see Permission to write views.
The algorithm used by Rational ClearCase considers the process’s user and group and the view-private file or directory’s owner, group, and protection mode to determine whether to grant execute permission for the file or directory. See Access algorithm for VOB and view data.