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 Submitted
Created by Guest
Created on Jan 27, 2026

Disallow a CDM job to run if the same job is running.

The current CDM job for scanning will import disks/volume groups to an IBM AIX server, create NFS exports, NFS mount the jobs to the Linux Sentinel server and then run the IE scan on the mounted NFS disks.  Once the scan is complete, the CDM process will unmount the NFS, remove the exports, unmount the disks from the AIX server and export the disks/volume groups from the AIX server.   This runs once every 24 hours.

However, should one of these jobs be delayed for any reason, the next day's job will start and attempt to do all the above steps while the first job is still running.  The new job will fail since it cannot do the steps.  The AIX server may be left in a state that will prevent ANY future jobs from successful completion unless/until manual cleanup is done.

We would like the system to not run the same job when a current job is running to prevent them "stepping" on each other, particularly when the jobs manipulate disk volumes/filesystems.  Having an option to allow or disallow a scheduled job to abort or wait for a previous job to complete is an acceptable option.

Idea priority Low