Skip to Main Content
Cloud Management and AIOps

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:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):

  • Cloud Pak for Multicloud Management

  • Cloud Pak for Network Automation - incl Orchestration and Performance Management

  • Cloud Pak for Watson AIOps - incl Netcool Operations Management portfolio

  • Edge Application Manager

  • IBM Observability with Instana

  • ITM-APM Products - incl IBM Tivoli Monitoring v6 and Application Performance Monitoring v8

  • Workload Automation - incl Workload Scheduler

  • Tivoli System Automation - inc Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)

  • Tivoli Application Dependency Discovery Manager - TADDM

If you encounter any issues accessing the Ideas portals, please send email describing the issue to ideasibm@us.ibm.com for resolution.

For more information about IBM's Ideas program visit ibm.com/ideas.

Status Not under consideration
Created by Guest
Created on Jun 11, 2015

Blacklist servers in Dynamic Pool

If we have problems with an execution server during our production day, how do we stop/blacklist this server in the pool. It is crucial for us that this can be done automatic. Our production day starts at 18:00CET with the majority of jobs starting at midnight and running until 08:00 in the morning. This mean that the support in the organization is very limited, so we need to make it automatic.

An example could be:
We have 50 jobs running on a pool with 3 servers. Pool is setup so only one job can run on each server at the same time. When started job1 and job2 starts fine on server1 and server2. Unfortunately server3 has some wrong configuration and job3 fails right after startup (not due to TWS settings, so TWS will assume job ran and another can start). Since job1 and job2 each takes 1 hour it means that all other jobs will be scheduled on server3 and therefore fail. End result is that out of 50 jobs only 2 will complete successfully.
1. If we set fence on a dynamic agent will this have effect on the pool (if fence is 50 on agent, then no jobs will start – assuming priority is lower than 50 on all jobs). Or is fence similar to limit and not being used by the dynamic pool when stated on the agent alone.
2. If a server returns certain error code for certain type of job, can we “blacklist” a server. Is there a simply way or do we need to make an event that takes the server out of the pool? Say all jobs named T-S-xxx fails with exit code 1. If the same job fails with exit code 2, then there are no problem. If another job type (for example named T-H-xxx) returns exit code 1, then there are no problem either.
3. Similar to the question above, if a server continues to return the same exit codes for different type of jobs we need to be able to “blacklist” the server. For example f we have 5 jobs in a row that returns exit code 5, then we might have to blacklist that particular server.
4. What if the job ends in state FAIL. This is often either a TWS error or configuration error of the job/server in TWS. Here we also need to “blacklist” the server.

Idea priority High
RFE ID 72623
RFE URL
RFE Product IBM Workload Scheduler (IWS)
  • Admin
    Marco Cardelli
    Sep 9, 2021

    This requirement is valid but we did not implement it until now because of other higher priorities enhancements. We close it for now, you may re-open it if the requirement is still needed.

  • Guest
    Nov 6, 2019

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Cloud
    Product family - Workload Automation and Control Desk
    Product - IBM Workload Scheduler (IWS)

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - ITSM Automation and Control Desk
    Product - IBM Workload Scheduler (IWS)

  • Guest
    Oct 23, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - ITSM Automation and Control Desk
    Product - IBM Workload Scheduler (IWS)
    Component - Product functionality
    Source - Other

    For recording keeping, the previous attributes were:
    Brand - Tivoli
    Product family - Automation
    Product - Tivoli Workload Scheduler (TWS)
    Component - Product functionality
    Source -

  • Guest
    Oct 22, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Tivoli
    Product family - Automation
    Product - Tivoli Workload Scheduler (TWS)
    Component - Product functionality
    Source - Other

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - ITSM Automation and Control Desk
    Product - Tivoli Workload Scheduler for Applications
    Component - Product functionality
    Source -

  • Guest
    Oct 21, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - ITSM Automation and Control Desk
    Product - Tivoli Workload Scheduler for Applications
    Component - Product functionality
    Source - Other

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - ITSM Automation and Control Desk
    Product - IBM Workload Scheduler (IWS)
    Component - Product functionality
    Source -

  • Guest
    Oct 21, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - ITSM Automation and Control Desk
    Product - Tivoli Workload Scheduler for Distributed (TWSd)
    Component - Product functionality
    Operating system - Windows
    Source - None

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - ITSM Automation and Control Desk
    Product - Tivoli Workload Scheduler for Applications
    Component - Product functionality
    Operating system - Windows
    Source - None

  • Guest
    Oct 10, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - ITSM Automation and Control Desk
    Product - Tivoli Workload Scheduler for Applications

    For recording keeping, the previous attributes were:
    Brand - Tivoli
    Product family - Automation
    Product - Tivoli Workload Scheduler for Applications