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 Future consideration
Workspace z/OS
Created by Guest
Created on Jul 11, 2024

Add include option to DSFS

There is only one valid value for HLQ_MODE and that is EXCLUDE. To enable controlled use of DSFS in production, HLQ_MODE=EXCLUDE is insufficient. What sense does the parameter make if there is only one permissible value, namely EXCLUDE? How would I have to define this exclude list if I initially only want to allow a few z/OS datasets for DSFS? We want to introduce DSFS step by step. To do this, it is necessary to be able to define the HLQ_LIST as an include list, and pattern matching must also be possible. Here's an example:

HLQ_MODE=INCLUDE

HLQ_LIST=USER1.*,USER2.*.CNTL,SP.SYSMOD.*

In this example, all files with HLQ USER1, all files from USER2 with the last level qualifier CNTL and all files with the HLQ SP.SYSMOD would be allowed. All other files would not be allowed.

Or completely remove the HLQ_MODE parameter and allow a combination of INCLUDE and EXCLUDE list statements. For example:

EXCLUDE=*

INCLUDE=SP.*.CNTL,SP.*.SRC,USER?.*.JCL

Idea priority High
  • Guest
    Reply
    |
    Jul 11, 2024
    This item will be considered and appropriately prioritized with other future candidates for a future release.