Skip to Main Content
Cloud Management and AIOps


This is an IBM Automation portal for Cloud Management and AIOps 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 Future consideration
Created by Guest
Created on Dec 28, 2023

Prevent RESUBMIT job stream plug-in job type to submit same stream multiple times within same minute

We have recently experienced some mailbox.msg corruption issues which are documented under case #TS014467118.
It was identified by HCL that the corruption is caused by the resubmit plug-in job type and occurs in memory.
We really identified many RESUBMIT plug-in job type running at very same second. Sometimes submitting the same job stream 3x within same minute. Which may be a contributing factor for the mailbox.msg corruption since the same submit command can still be under in memory processing causing TWS to do not manage the messages accordingly.
Even with the "Start after" option set to 00h01 within the job definition to prevent this scenario, would be a good idea to prevent the users define something that can crash the system.

Idea priority Low