Skip to Main Content
IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. 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 Not under consideration
Workspace z/OS
Categories z/OSMF
Created by Guest
Created on Jan 22, 2026

Allow multiple validation criteria for String type Variables (Type and Length at a time)

1) Problem Statement (Current Limitation)
Today, z/OSMF variable validation for String type supports either:

Type-based validation (Validators like DSNAME, DSQUAL,ALPHA etc.), or
Length-based validation (minLength, maxLength),

…but not both simultaneously for the same variable.
This leads to:

Extra manual checks in JCL/properties/scripts,
Higher error rate (invalid DSNAME length or invalid characters slip through),
More UI complexity for users who must infer constraints rather than seeing them enforced.


2) Proposed Solution: “Composable Constraints” Validation Model
Introduce a model where multiple validators can apply to the same variable, evaluated as a logical AND by default.
Key principle
A variable can declare:

Primary semantic type validator (e.g., DSNAME)
Optional additional constraints:

minLength, maxLength
Regular expression based validation

 

This is essentially:

“Validate as DSNAME and enforce max length = 44”
instead of “either DSNAME OR length”.

Idea priority High
  • Guest
    Jan 28, 2026
    .This idea asks for function that can already be accomplished using an existing feature. Additionally, changing this behavior could cause users to encounter additional issues as well as requiring many changes to existing code as well and the underlying workflow schema. Following is detailed explanation:

    The validation types mentioned, such as DSNAME, are just regular expressions that can be found in the workflow schema. For example, the regular expression used for DSNAME can be found in the workflow schema:

    <!-- DSNAME: A-Z, #, $, @, }, - or 0-9
    regexp: ^(?=.{1,44}$)[A-Z#$@][A-Z0-9\}#$@-]{0,7}([.][A-Z#$@][A-Z0-9\}#$@-]{0,7}){0,21}$
    -->

    This regular expression already includes max length of 44 built into it, and if a customer would like to modify this expression to add more rules or adjust the max length of the string, we already allow for custom regular expressions to be used as a validator.

    Additionally, changing this behavior to allow for the user to effectively set multiple regex's to be applied to the same string could result in contradictory regex statements
    For a simple example, all 3 settings could effectively set different values for the length of the string, or the regex statements could become compatible.