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

Workload Automation

Showing 281

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

Provide kerberos support for IWS REST API

Currently the IWS REST API only supports basic authentication (usage of hardcoded user/password combination). We need to implement the REST API using just a userid with no password.
over 6 years ago in Workload Automation 1 Future consideration

Ability to add more than one prefix in monitor job and monitor jobstreams

We like to be able to add more than one prefix in the 'Task Name' field when creating a new job or job stream monitor.
over 7 years ago in Workload Automation 1 Future consideration

Allow Mailman Server to continue processing other servers after a failed server

Please refer to We have 20 servers under the control of a single Mailman server , Which processes the message queue. We had a failure on 1 server , which in turn caused ALL other server messages NOT to be processed. which eventually IWS believed t...
about 2 years ago in Workload Automation 0 Future consideration

Allow installation and patching via sudo rule instead of requiring actual root access

Our security teams do not like providing us access to root to perform installations and patching activities. Their stated preference is that we use sudo rules. Having to coordinate the activity with the Linux admins means double the human resource...
about 2 years ago in Workload Automation 2 Future consideration

The job description cannot be displayed in the job flow view.

My client wants to see the job description in the job flow view.The job description is not be displayed, but the user wants to see it in the view.Since the description contains useful information which is the user want to see in the job steam flow.
about 5 years ago in Workload Automation 4 Future consideration

Tool for use in converting of .txt file based scheduling object definitions to .json as payload in the REST requests.

Currently using TWS version and are leveraging TWS REST API to create a robust CI, CD workflow to deploy objects like JOBS, SCHEDULES, RESOURCES to TWS servers. At this point all the TWS objects definitions available in a .txt file using syntax me...
over 1 year ago in Workload Automation 0 Future consideration

Can we have different Dependencies on Runcycles

extend the function on Runcycles
over 1 year ago in Workload Automation 0 Future 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...
9 months ago in Workload Automation 1 Future consideration

On linux JOB the JobManager should expand environment variable (if used) in stdout and stderr definition

On a JOB kind "executable" if we use environnement variable in stdout and stderr definition : they are not expanded as they should. May bhis include this another enhancemnt : possibility to add a ".profile" in configuration list of the JOB (becaus...
9 months ago in Workload Automation 0 Future consideration