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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - 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 Jun 15, 2017

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 interpreted as relative to the start time of the previous run. With the earliest start time the rerun frequency is interpreted as absolute from the earliest start time of the previous run, with the quirk that if any run times are missed all but one of the missed runs is skipped leading to the job running bunched up; for example a job that runs hourly the 1:00 PM run is placed on hold, at 3:10 PM it is released at which time it runs and a 3:00 PM earliest start time job is created by the rerun frequency and it runs at 3:11 PM.

We need to have full control of how the rerun frequency is interpreted regardless of whether an earliest start time is defined on the job. That would be: a choice of Relative or Absolute, and for Relative there should be a sub-option of "from previous start time" or "from previous end time", and for Absolute there should be a sub-option of how many missed runs to skip, from "none" to "all" with "all-but-N" between. These options should be per each job in a job stream that has a rerun frequency.

Idea priority High
RFE ID 106559
RFE Product IBM Workload Scheduler (IWS)
  • Guest
    Mar 30, 2022

    We recognize the validity of this requirement, but since there is at least one way to manage this kind of scenario, we do not plan to implement it soon because of other higher priorities. So we close it for now, you may re-open it if 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)