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
Created by Guest
Created on May 28, 2024

allow more than 1 DASD to be specified in RTE_PDS2_VOLUME for PDSV2 datasets

The current RTE_PDS2_VOLUME parameter only allows "ONE" VOLSER to be specified as the target DADS for allocating PDSV2 datasets.

But,

(1) not all customers are using SMS to allocate PDSV2 datasets

(2) in case if customer installs a full suite of ZMS OMEGAMON products (e.g. z/OS, CICS, DB2, MQ, Storage, Network, JVM ... etc), and increase the FILE_COUNT and STORE_SIZE, then the total DASD size would be significant, and would need to spread over multiple 3390-9 DASD. 

The only option is to reduce the PDSV2 dataset size, or change the target DASD to be model-27 or model-54.

But this is workaround, not flexible.

Idea priority Medium