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 Delivered
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
  • Admin
    Marco Cardelli
    Dec 13, 2023

    Delivered in the lates Kubernetes job type plug-in version.

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