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 Not under consideration
Created by Guest
Created on Jan 15, 2015

add feature so that jobs in USERJOBS can trigger events for total duration

There is a significant portion of jobs that get placed into USERJOBS that are hung. We need a way to trigger events for total duration of the job, such as at 24h duration, or 72h duration. Currently there are 2 limitations in TWS that are preventing us from doing this: currently duration events are created with a timer starting when the job starts runnning and timing out before the job completes; there is no event generated to begin the timer for jobs in USERJOBS, so a start event could be created when jobs are placed into USERJOBS but then the second limitation comes in that the timer would need to be set to diffent time-outs for each job depending on when they started and there is no way to parameterize the time-out value in this way.

Idea priority High
RFE ID 64476
RFE URL
RFE Product IBM Workload Scheduler (IWS)
  • Guest
    Reply
    |
    Feb 8, 2022

    This requirement is not in plan for 2022 and it's been open for a long time. So we close it, please re-open it in the future if still needed.

  • Guest
    Reply
    |
    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
    Reply
    |
    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 Distributed (TWSd)

    For recording keeping, the previous attributes were:
    Brand - Tivoli
    Product family - Automation
    Product - Tivoli Workload Scheduler for Distributed (TWSd)