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.

ADD A NEW IDEA

Workload Automation

Showing 462

Improving Resiliency #3: gracefully resuming TWS services even after a sudden TWS stop

Event in a scenario of a sudden TWS Stop (abrupt kill of TWS services), the TWS Agent needs to have the capability of gracefully resuming its services after a failover.
about 1 year ago in Workload Automation 0 Future consideration

Improving Resiliency #1: re-attaching "running OS processes" in secondary node after a failover

Whenever a failover happens, we need the Agents to be capable of re-attaching the running OS processes (attached to each individual SAP Jobs) when its services are restarted/failed-over from Site A to Site B.
about 1 year ago in Workload Automation 0 Future consideration

over-come event watcher limitation

Hello, Whenever file watcher event fires for the first time, relevant file should not be in server path, else IWA consider it as old file and fails to submit the job. through an IBM case we came to know that it is a limitation of IWA. Due to this ...
over 1 year ago in Workload Automation 0 Planned for future release

DWC - Filters Improvements

We have more than one team that manages the production environment and in most of the time each team takes care of a group of applications running under IWS. Using standards for Job, JobStream and Resource names we managed to create filters that c...
over 5 years ago in Workload Automation 1 Future consideration

filter criteria TDWC

On TDWC Console, to filter the Jobstreams in one views? when we create a new task , and on the 'General Filter' Page, under the 'Filter Criteria', Is there anyway he can specify more than one Jobstreams in the 'Job Stream Name' Text box so that he...
about 13 years ago in Workload Automation 6 Planned for future release

Locate Dependency Loops in DWC(Show Plan View)

This makes Dependency Loops graphically visible in the Show Plan View option
over 2 years ago in Workload Automation 1 Future consideration

Dash Board Assistance Required

Assistance required for Centralized Dash Board across multiple applications.
over 3 years ago in Workload Automation 7 Not under consideration

Rerunning the single job does not create a new log but overlays the old log

Good evening, we have an idea about the functioning of job rerun in the case of individual jobs not belonging to a Jobstream. When we rerun a single job within its flow it correctly creates a duplicate entry of the same job on the console with a n...
7 months ago in Workload Automation 1 Future consideration

Putting module EQQSSCNMx above the line

Due to administrative rules we are forced to run multiple IWSz Systems in parallel on one SYSPLEX. When migrating IWSz we are using BUILDSSX REBUILD and SSCMNAME TEMPORARY to avoid IPLs. After migration we are restarting IWSz with SSCMNAME PERMANE...
over 4 years ago in Workload Automation 0 Future consideration

One Tracker per LPAR serve all Controller

Due to administrative rules we are forced to run multiple IWSz Systems in parallel on one SYSPLEX. So we have to start tracker STCs for each of our multiple IWSz controllers on every system of the SYSPLEX. As the tracker STCs all do the same work ...
over 4 years ago in Workload Automation 0 Future consideration