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.
See this idea on ideas.ibm.com
Currently, (with certain limitations) it is possible to archive files via the TSM API and retrieve them via the standard TSM client. Unfortunately, the reverse is not possible: It is not possible to archive files via the standard TSM client and later retrieve them via the TSM API. Lifting this restriction is the subject of this enhancement request.
The reason we require this functionality is so that we can move away from using the TSM client and directly use the TSM API. This will allow us to automate some things that aren't possible today and also improve performance (the biggest benefits are the possibility of streaming data and requesting partial byte ranges). The issue for us is that we have 15 years of existing data on our TSM systems (a little over a petabyte) which we currently wouldn't be able to retrieve via the TSM API since it was all archived via the TSM command line client.
Note that we don't need access to file attributes such as ACLs or anything. We would only need access to minimal file-like attributes already supported by the API along with access to the byte stream of the file(s).
Idea priority | High |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
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
Our apologies for the delayed response in the final disposition of this request. We understand the request and the need unfortunately, lifting this restriction is not in alignment with our present multi-year strategy. We are exploring other solutions that might align with the desires of this request but it is not in plan for the near term.
The private RFE section does not seem to be editable? (I assume you meant the "Business justification" section?) Can you make this editable so I can add more information privately?
Thanks.
can you please provide more information about the use case for this enhancement request? you can specify this info in the private section of the RFE so it's not shared publicly, we're specifically looking for information about why do you think this would be useful to TSM customers? the standard TSM client that had archived the data still exists in the environment and can retrieve that data, where (and why) do you think the API client needs to pull this data?