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 Aug 26, 2025

Maintain Utility: Add more Allocation parameters for database DSGs and Image Copy sizing.

Currently, the VOLALLO parameter applies to all database datasets including all DSGs as well as image copy datasets.  It would be useful to have separate command parameters for allocations of DSGs and Image copies because these datasets typically are not one blanket size.  Image copies are usually smaller than the database datasets and, DSG's contain a variety of segments different from the primary DSG which frequently results in varying DSG dataset sizes.  

Creating more granularity for the allocation of these datasets would benefit those who would like to exercise control over dataset allocations and prevent overallocation of these datasets.  Also, this would help to minimize the possibility of B37 errors that may result when MAINTAIN  requests more space than needed for DSGs and/or image copies.  

Currently, there is a VOLALLO, VOLALLOL and VOLALLOX parameter.  I believe that adding a parameter for image copy allocation such as VOLALLOI for example, would be useful.  And, for DSG's providing VOLALLO2/3/4 or VOLALLOB/C/D to control DSG allocation would be useful.        

Idea priority Medium
  • Admin
    Tracy Dean
    Sep 28, 2025

    This Idea is accepted. The target delivery date is not yet determined.