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 updateson 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
block client side CCRTC integration with setting in server.conf
Following TS001302012 pvob cmi setting to disable client side RTC integration which was implement in a complex way when having numberous of PVOBs and multiple RTC instances. I got that answer
L3 says that cmi settings are always per provider, wether at stream or pvob level. You may set it with a repetition (loop) of this command: cleartool mkcmprovider -vob -data -replace cleartool mkcmprovider -vob -data -replace ...
L3 also said it could possible to implement a setting in server.conf outside of cmi context. That setting would block client side integration for all web/automatic views of a CCRC server. If you're interested then file an RFE and I will forward the RFE ID to L3: https://www.ibm.com/developerworks/rfe/execute?use_case=submitRfe
Kind Regards/Cordialement, Jean-Claude Staquet
So please implement asap that blockage of client side CCRTC integration with setting in server.conf
Do not place IBM confidential, company confidential, or personal information into any field.