This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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
Add physical bytes used on media to QSRSAV format for save output
We currently have no way to know how much space is used and how much is available on our LTO media until we fill the tape. The save commands support output to a file in QSRSAV format, which includes the original size of the objects that were saved, but we do not know how well these objects compressed, and the size reported for logical files is there total size including the access paths even if the latter is not being saved.
The products we use for our Windows and Linux server backups are all able to tell us how many bytes were physically used on the tape after compression. Ideally, I would like to see this value in a new field on the QSRSAV format so we could calculate the actual bytes used vs. the known media capacity. If this could only be provided as a total for the tape file (volume sequence) and not individual objects that would still be a lot better than what we have now. Alternatively, if there is some way to compute this from the SROPSN "Starting position in file" value, documentation of that would be useful.
We do not use BRMS and have no desired to do so as we have our own internal software for managing volumes across multiple different platforms.
Do not place IBM confidential, company confidential, or personal information into any field.