Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software 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 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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Categories Wazi Deploy
Created by Guest
Created on Jul 17, 2025

Improve documentation of data available in jinja2 templates

We use jinja2 templates to generate JCL submited by job_submit templates. We often need to loop trough the artifacts 
and generate jcl. For us it is not clear what data wazi provides that can we can exploit in the templates. 

there is a note on this page but it is not really a documentation of the data structures. 

https://www.ibm.com/docs/en/developer-for-zos/17.0.x?topic=translators-coding-variables-in-jinja2-templates

We need proper documentation of this data and also information on interface changes so that we can manage our jinja2 templates. 

One missing information is the target dataset in the artifacts dictionary. We often need to generate DD statements with PDS datasets, for example

//BINDPKG  DD *
{% for artifact in step.artifacts -%}
//*        DD DISP=SHR,DSN={{environment.hlq}}.PKG({{ artifact['name'] }})
{% endfor %}

 

In this case it would be great if we could code artifact['target_dataset'] (new property)

//BINDPKG  DD *
{% for artifact in step.artifacts -%}
//*        DD DISP=SHR,DSN={{artifact['target_dataset']}}({{ artifact['name'] }})
{% endfor %}

 

Idea priority Low