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 Feb 12, 2016

allow job time dependency to be set relative to job stream input arrival to fix timezone DST issue

Allow job time dependencies to be set relative to the job stream input arrival time rather than from the Plan start time as it is currently. This is important for scheduling where the time zone of the workstation has different Daylight Savings time days than the master and the job dependency is within the time that moves from the beginning of the day to the end of the day depending on the DST alignment. The job stream can be scheduled for a time that does not move from beginning to the end of the Plan and a job could have a dependency after that time such that it would always run on the correct day, such as the example below that should always run 3 AM in the early morning of the first day of the month.

For instance it could be implemented in the Scheduling language as:

SCHEDULE SERVER#JOBSTREAM TIMEZONE America/Mexico_City
ON RUNCYCLE RC1 "FREQ=MONTHLY;INTERVAL=1;BYMONTHDAY=-1"
AT 2300
CARRYFORWARD
:
SERVER#JOB
AT 0300 AFTER_IA
END

Idea priority High
RFE ID 83955
RFE URL
RFE Product IBM Workload Scheduler (IWS)
  • Admin
    Marco Cardelli
    Mar 21, 2022

    The requirement is valid but not high priority for next year, so for now we close it. Please re-open if you still have this need.

  • 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)