Skip to Main Content
Cloud Management and AIOps


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation 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

Clear

Workload Automation

Showing 118

Cancelation of WebSphere batch job (wsgrid.bat) on Windows should invoke shutdown hook i java

Cancelling a WebSphere Batch job on Windows, a java.exe process started from the wsgrid.bat only kills the java process. The shutdown hook in java is not called and the job/step i the websphere bacth container is not interrupted/stopped. This is "...
almost 10 years ago in Workload Automation 3 Not under consideration

Jobstream should go in ABEND status if one job in the stream is in error

A jobstream should go in ABEND status if one job in the stream is in error even if other jobs in the stream are in EXEC status.
over 8 years ago in Workload Automation 2 Not under consideration

Possible to see workstation pools associated or defined for an agent workstation.

TWS version 8.6.0.1TDWC version 8.6.0.1Possible to see workstation pools associated or defined for an agent workstation.In critical situations where a server with a TWS agent goes down or have severe performance problems, it is necessary,to identi...
about 13 years ago in Workload Automation 7 Not under consideration

allow job time dependency to be set relative to job stream input arrival to fix timezone DST issue

Allow job time dependencies to be set relative to the job stream input arrival time rather than from the Plan start time as it is currently. This is important for scheduling where the time zone of the workstation has different Daylight Savings tim...
almost 10 years ago in Workload Automation 2 Not under consideration

Increase the Limitation on 16 Characters for the JobStream name

Increase the Limitation on 16 Characters for the JobStream name. I
over 10 years ago in Workload Automation 3 Not under consideration

Mandatory predecessors for TWSd.

In TWS 9.1 is announced a new type of predecessors who allow waits for at predecessor, which is not in the plan at Make-plan time. But this new type is only deliveret to TWSz in TWS version 9.1. Please also deliver the mandatory predecessor type f...
almost 11 years ago in Workload Automation 3 Not under consideration

Add historical reporting features available on IWS to IWS on Cloud.

IWS on Cloud (SaaS) does not provide the historical reporting features available in the on-premise versions. The "historical reports" features should be available to SaaS customers too. The priority is on "job run history".
almost 7 years ago in Workload Automation 1 Not under consideration

control rerun frequency interpretation

Currently when a rerun frequency is defined on a job in a job stream that frequency is interpreted differently depending on whether there is a job level earliest start time on the job. Without the earliest start time the rerun frequency is interpr...
over 8 years ago in Workload Automation 2 Not under consideration

List workstations in dynamic pool the same way as its possible for pools in TDWC/TWS

When using dynamic pools with "ordered list" it's difficult for operators to see which workstations that are active/defined in the pools.Should be possible to answer questions like:1. Is the agent part of a pool2. which agents is in a poolRFE 2254...
over 13 years ago in Workload Automation 3 Not under consideration

Ability to restrict the Rest API to specific user groups and rate-limiting

Currently, the Rest API can be used by anyone with access to the engine. We would like the ability to restrict that access to a specific user group or even source IP address or subnet. In addition, being able to rate limit Rest API calls would als...
about 1 month ago in Workload Automation 1 Not under consideration