Skip to Main Content
IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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 Planned for future release
Created by Guest
Created on Mar 20, 2026

Request to document the usage of variable reference syntax `@{var.<index>.<variable_name>}`

EWM supports a variable reference mechanism that allows the pattern: `@{var.<index>.<variable_name>}`

Where:
- `<index>` - A numeric index (e.g., 1, 2, 3) that identifies which translator in the language definition the variable belongs to
- `<variable_name>` - The name of the variable being referenced

However this mechanism is not documented.

For example, such variable can be used to define 1 translator to compile multiple COBOL versions like v6.2 or newer versions.
Multiple TASKLIB datasets for SIGYCOMP v6.2, 6.3, 6.5 and added to the translator concatenation with conditions like  <equals arg1="${COBOLVERSION}" arg2="62"/> or <istrue value="${isV62Compiler}"/>. 
COBOLVERSION or isV62Compiler are defined as translator variables (i.e COBOLVERSION=62 or isV62Compiler=true)
and on the language definition as COBOLVERSION = @{var.1.COBOLVERSION} or isV62Compiler = @{var.1.isV62Compiler}. 
The numeric index (e.g., `1` in `@{var.1.COBOLVERSION}`) indicates:
- **Position reference**: Refers to the first translator in the language definition
- **Multiple translators**: If a language definition has multiple translators, use `@{var.2.VARIABLE}` for the second translator, `@{var.3.VARIABLE}` for the third, etc.

 

Idea priority Low
Needed By Not sure -- Just thought it was cool
  • Guest
    Apr 23, 2026
    The EWM Ideas Review board looked at this request and decided to keep it on the Backlog as an uncommitted candidate for a future release.