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 DFSMS SMS
Created by Guest
Created on Oct 17, 2016

Attempting to use SPACE CONSTRAINT RELIEF dataclas atribute allocation after a failed multi-striping allocation

To attempt SPACE CONSTRAINT RELIEF single-striping allocation after a failed multi-striping allocation.


As the level2 support had explained in PMR 50100,228,631 , when a multi-striped sequential dataset allocation fails ( Sustained Data Rate greater than 0 was specified in STORAGE CLASS and there is no sufficient space to satisfy the request in at least one stripe in the storage group ) then the SPACE CONSTRAINT RELIEF data class atribute cannot be used because SMS has already chosen its allocation path, the striping allocation path (i.e. IGDVTSTR), which do not consider space constraint relief.

But trying to use SPACE CONSTRAINT RELIEF after a failed multi-striping allocation could be successfull because it is easyer to obtain the original amount of tracks requested when there is no a requesite to have exactly the same number of tracks in each volume. SPACE CONSTRAINT RELIEF single-striped multi-volume allocation is less exigent than MULTI-STRIPED allocation.

So, the RFE target is to change the striping allocation path so that SMS tries a single-striped multi-volume allocation using SPACE CONSTRAINT RELIEF when the original multi-striping allocation fails. Or the equivalent, trying the non-striping allocation path after a failure in the striping allocation path.

The L2 Support considerations for PMR 50100,228,631 follow:

In the case where the data set is allocated as multi-striped (SDR is NOT 0 or blank), SMS uses the striping allocation path (i.e. IGDVTSTR) to allocate the data set. This path is where the reduction of stripes is performed. Even if we get to a single stripe in this case, we are still in the striping allocation path and this path will not consider space constraint relief.

In the case where SDR=0 or is blank implying a single striped data set is to be allocated, we do not go down the striping allocation path and this will use the non-striping allocation path which will consider space constraint relief if necessary.

Idea priority High