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 Other/Unknown
Created by Guest
Created on Dec 2, 2019

IDz: Allow IDZ user build variables to be generated from RTC language definition/translator instead of manually via IDz Prefs

In an IDz user build, DDNAMEs using variables as STEP RCs in a build have to be defined manually in the context of the z/os project.
Normally, the STEPS and initBuild are defined as properties of the language definition by navigating to IDz Window/Preferences/User build and click Add on table "Define property names and values to be used during user builds".
The error received is an error fetching the translator if the variable values aren't in the properties. This causes values not to be found.

These should be picked up by the language definition and translator automatically and not have to be manually defined.

"I think it is wrong to ask the user to add the variable names which refers to the step Return codes.
The reason for adding the step names in the build definition is for simple references to the RC from the individual steps.
By default the RC is assigned to RC variables with the step number (1,2,3... etc). so these variables should already be created, and thus should have all the needed definitions needed."

Idea priority Medium
  • Guest
    Reply
    |
    Jan 16, 2020

    Thank you for taking the time to suggest an enhancement to our product. Many of our product enhancements result from feedback from our customers, so your input is always very important to us. Your request is currently inline with our product strategy and we have planned it for a future release of the product. Thank you for your suggestion and continued support.

  • Guest
    Reply
    |
    Dec 18, 2019

    A preliminary evaluation of this request indicates that it is consistent with our business strategy. Further evaluation of this RFE is underway.