Skip to Main Content
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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. 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.

Status Is a defect
Created by Guest
Created on Jul 6, 2017

TSM Macro for Capacity Licensing does not differentiate between Capacity and PVU

Our team uses TSM 7.1.3.100 to backup our entire enterprise. We currently are licensed by Terabyte; however, we also use TSM for System Backup and Recovery (Sysback). Sysback is licensed by PVU. We are in the middle of an IBM Software audit and the provided macros to show capacity usage does not differentiate how the data is being backed up.

Idea priority High
  • Guest
    Reply
    |
    Jul 11, 2017

    This is a defect and should be pursued via an APAR. Please re-engage with IBM Support.