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 Under review
Created by Guest
Created on Sep 12, 2024

Enhance the Configuration Manager validation step to warn about undefined symbolics

With RTE_SYSV_SYSVAR_FLAG=Y, when a (user or system) symbolic is used in a &SYSNAME. configuration, and that symbolic is not defined in either the VAR$&SYSNAME. or as a system symbolic. Examples would be:

RTE_TCP_PORT_NUM "&NONE_EXIST_SYMBOL."

or

GBL_USS_TKANJAR_PATH "&NONE_EXIST_SYMBOL."

The Configuration Manager GENERATE OPTION VALIDATE step will not flag these symbolics as undefined/missing (nor does the GENERATE OPTION PREPARE). Only the CM GENERATE step will fail (with RC=08). It would be good if the GENERATE OPTION VALIDATE, would flag (with a warning) any missing symbolics and return a condition code of 04? This allows a batch job to stopped or continue based on the GENERATE OPTION VALIDATE condition code, i.e. for DEPLOY one may choose to ignore a condition code of 4, but otherwise one may want to validate that these missing symbolics are indeed acceptable.

Idea priority Medium