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 Not under consideration
Created by Guest
Created on Mar 18, 2015

granting authority to a domain and subsequently adding nodes to the domain

- Granting tsm admin accounts node AUTH=ACCESS doesn't appear to allow them to log in to the locally installed BACLIENT GUI but the Web GUI works…. Is this Expected behavior? Client OWNER privilege works fine in both…. But what permissions does this grant with filespaces? Can they delete/rename existing filespaces/archives? We were hoping to not give them authority to modify or delete existing filespaces or archives. Any way we can get this done while still allowing them backup and restore capabilities from the installed GUI as well as the Web Client?

- Currently we grant admin authority to nodes at a domain scope. We've noticed that if a new node is registered to TSM and belongs to a domain that a tsm admin has privilege to, the node is not automatically added to the list of accessible machines. Is this intended behavior? What can we do to help with this? Only thing I can think of is admin scripting a revoke and grant command for the users?

Idea priority Urgent
  • Guest
    Reply
    |
    Jan 8, 2021

    This request may not be delivered within the release currently under development, but the theme is aligned with the current multi-year strategy. IBM may consider and evaluate any RFE Community feedback for this request through activities such as voting. IBM will update this request in the future.

  • Guest
    Reply
    |
    Jun 12, 2015

    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