This portal is to open public enhancement requests against IBM System Storage 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Storage
Product - Tivoli Storage Manager (TSM) Family
For recording keeping, the previous attributes were:
Brand - Tivoli
Product family - Storage
Product - Tivoli Storage Manager (TSM) Family
Thank you for submitting this enhancement request, and please accept my apology for the long delay in replying, we have provided this function to automatically turn on CBT (when the appropriate pre-requisites are met) with 6.2.2 back in 2011, there might be something in your specific environment that needs to be addressed and this should be treated via the PMR/APAR route and not as a product enhancement, please open a support call on this issue.
Thanks for submitting this enhancement request, we did not see enough details in this requirement to have a significant discussion and a meaningful response, please provide more details about this requirement including the business reason (impact to SLAs, reduced RPO etc.), technical functionality (what are you trying to achieve, and why do you think it should be done in this specific way etc.), some additional details about your current environment (for example a TSM 6.2 server running on AIX, the client is running on RHEL etc.) and any particular reason why the current implementation and best practices aren't meeting your requirements we believe that what you're describing in your request is the actually the way TSM for VE 6.3 is currently behaving