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 Planned for future release
Created by Guest
Created on Dec 29, 2021

Setting a TWS date parameter within Kubernates yaml file path on TWS script

We need to pass parameters to JCL during runtime, not only for a job, but for all jobs in general. Since the job is created directly by Kubernetes via the plug-in, the parameter given from JCL needs to be transferred to Job.yaml.
Idea priority High
  • Guest
    Dec 30, 2021

    In details;


    a. When scheduling the kubernates batch on TWS, we have two options. The first option is to prepare a batch content by giving the yaml file path. The second option is to prepare batch content (job in the JOBLIB) directly with yaml content.


    b. If we prefer the second way, the content of the yaml file is completely appended to the batch content. So, we can set a variable such as "&OYMD." by using "//*%OPC SCAN" in the batch content.


    c. But, if we choose the first path between these two options, it only adds a file path to the batch content that DWC produces. So, we have to add the "&OYMD." date parameter into the yaml content. Since we add the yaml file via the file path, we cannot set the parameter in the batch content when it executes.


    d. What I am trying to explain here is not the yaml file path that we want to pass to the parametric structure. What needs to be parametric is a value equivalent in the content of the yaml file located in this file path.