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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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 - including Orchestration and Performance Management
Cloud Pak for Watson AIOps - including Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - including IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - including Workload Scheduler
Tivoli System Automation - including Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
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.
Do not place IBM confidential, company confidential, or personal information into any field.