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 Dec 2, 2016

Improve NQR Performance

When doing an NQR on Nodes with tens of millions of files, the initial TSM database search and sort operation which takes place on the server takes several hours.
We noticed that the hardware resource utliziation (CPU, DB2 Disks) is not very high during this procedure.

DB2 uses 60% of a single core
dsmserv uses 50% of a single core

DB2 DB Disks are utlized 25%
DB2 Logs are utlized max 15%

Seems that this process runs single threaded and not very well optimized.

However having a good RTO perspective when using TSM also on large Nodes is crucial if TSM should succeed in the future.

Telling users: "Well now we have to wait 1 day until TSM is ready and begins to send back your data" is no option and Nodes with several tens or even hundreds of millions of files is not that uncommon even today.

Idea priority High