Skip to Main Content
IBM System Storage Ideas Portal
Hide about this 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.

extend mmapplypolicy --scope

See this idea on ideas.ibm.com

I have a filesystem with >1300 independent filesets and ~540 million files. Running mapplypolicy with --scope filesystem takes a long time because all inodes need to be scanned.

For some mmapplypolicy runs I only need to process one fileset so I can switch to --scope fileset which makes the scan much quicker.

But if I need to apply a policy to two or more filesets at once (using -i <inputfile>) I need to switch back to --filesystem.

So my suggestions is to extend --scope with an "auto" or "smart" mode that limits the run to the filesets (or inodespaces) that are connected to the entries in the inputfile instead of scanning the whole filesystem. 

In addition, if all policy rules are limiting the selection with FOR FILESET(fileset1, fileset2, fileset3) mmapplypolicy's scan could be reduced to the given filesets.

Both these changes would significantly improve the runtime of policy runs.

Idea priority Medium