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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Needs more information
Created by Guest
Created on Apr 30, 2024

Summary of how time is spent on a job in dsminstr.log - i.e. by percentage to easily determining the primary bottlenecks

Currently, all the information in the dsminstr.log is by thread, and it would be fantastic to know how to summarize this information on a job-level.

This is very hard - if not impossible - to do in the current state, as all information is per thread, and these are running simultaneously, so even if you add up the numbers you do not get a clear picture. Often what is needed is just to know how the time is spend in percentage - to know the primary bottlenecks and know where to focus your time and ressources to improve performance.

Veeam does this nicely by specifying where the waiting time is spend - i.e. 80% of the time is spend waiting on the source system (ESXi/vSphere):

"Load: Source 99% > Proxy 14% > Network 0% > Target 0%   - Primary bottleneck = Source" 

The dsminstr.log already holds all the relevant information, so is somebody could create a tool to summarize this information (i.e. a perl/python script), that would go a long way - or even just document how the information should be summarized on a job level.

Ultimately, the  source should be changed, so that this  info could be found at the bottom of the dsminstr.log.

Idea priority Urgent
  • Admin
    Juan Carlos Jimenez Fuentes
    May 2, 2024

    Hi, can you please share more details on the impact of not having this functionality? Thank you!