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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
I agree with your solution to this RFE. That should work well for us. Thank you.
Due to the concern about number of extents per volume a data set can have and about the potential space the data set needs to be extended, SMS will still attempt to preserve number of candidate volumes in Catalog for a data set. Therefore, to satisfy this RFE, SMS will enhance the behavior of Extend Storage Group Name attribute in a storage group definition as follows:
During initial non-striped, non-Guaranteed Space allocation, when the number of volumes in an enabled (primary) storage group is less than the number of volumes requested, volumes in the enabled (primary) storage group are not marked for the tertiary list if all the following conditions are met:
1. The enabled (primary) storage group has an extend storage group name specified.
2. The difference between the number of volumes in the enabled (primary) storage group and the number of volumes requested can be covered by the number of volumes in the extend storage group.
3. The primary requested space can be satisfied in the enabled (primary) storage group.
If all the above conditions are met, the data set allocation will be attempted in the enabled (primary) storage group.
The data set volume count is still preserved and stored in Catalog as requested.
Volumes in Overflow and Extend storage groups are still not eligible for the primary list.
Note: If all volumes in the enabled (primary) storage group are EAV, USEEAV(YES) in SYS1.PARMLIB(IGDSMSxx) is still expected for SMS to be able to select EAV volumes.
Please provide the feedback for our proposed solution.