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 Submitted
Created by Guest
Created on Jun 27, 2024

Job Management Plugin needs to be able to rerun jobs in different Streams

For a very simple process that needs to rerun a job in the same stream this works fine. But the use of this would more likely be handled by a simple job rerun setting or maybe a recovery job. To make this far more useful the plugin should also be able to rerun a job in any other Stream that's on the plan. 

To make this plugin a significant tool in the scheduling toolkit, the ability to rerun any job in the daily plan, in any stream, makes it ideal for complex scheduling scenarios and loop control, as was my intended use.

This would offer ever scheduler significant benefit for complex scheduling requirements.
The use of this plugin means Users can be provided template jobs and therefore avoid the need to share TWS administration access. (Posing a security risk)
The only work around for this is to create a job that calls conman to rerun the job in a different Stream, This is where risk starts to be relevant.

Having the plugin available, means that the users can run specific plan actions against their own workload prefixes, without the need to submit jobs to the TWS Masters directly as conman commands.

Idea priority High