IBM System Storage Ideas Portal
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).
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.
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
Unfortunately we were unable to implement a solution to this enhancement request due to other requirements that were of either higher demand by the market or higher priority and there still remain no commitments to deliver a solution in the next release or two. If you would like us to reconsider this suggestion after the next release of the product, please resubmit your request.
Hi. This reminds me of a change made a long time ago to the 'del volh' command. As I remember, the initial implementation did not require the
TYPE parameter; if none was supplied it defaulted to all. This was very
dangerous! A change was made to remove the default and require the
TYPE parameter. Regarding 'del fi', I know I have entered it without the type and deleted archives when my intention was to just delete the backups.
I think removing the default and requiring TYPE for delete filespace is a good idea.
Description:
Function needed to eliminate the possibility of unintentionally deleting data using the 'delete filespace' command. Default should be type=none vs. type=any. Requirement should be that specific parameter(s) be entered as an argument based on the type of data requiring deletion. Remove the TYPE=ANY argument altogether. Force administrator to indicate all data types separately with comma delimiter.
Thanks for submitting this RFE, unfortunately, this does not contain enough details 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.), reason why current implementation and best practices aren't workingm and some additional details about the current environment (for example a TSM 6.2 server running on AIX, the client is running on RHEL etc.) we need these details to fully understand this requirement and discuss it, currently it only says: "Eliminate the possibility of unintentionally deleting data"