Cloud Platform
This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
The ClearCase VOB database server processes (vobrpc, vob, db) access the VOB with the "effective user ID" of the VOB owning user, and the view server processes execute with the credentials of the view owner. In order for the logs to be collected, they have to at least default to "world" writable. If you can ensure that the VOB and view owners will be a member of a single group (a "ClearCase users group") and that group will be presented on view/VOB creation as one of the first 16/32 groups, you can reprotect the logs to 664 or 660 with the owning group being the cc users group.
The only possible fly in the ointment is the weekly log scrubbing task, which may recreate the log files as it scrubs them. A custom job can be created to reset the permissions as desired, and that job can be scheduled to run after the log scrubbing task.