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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
.Reopening this RFE based upon last comment and referenced RFE. In the future we will take a wider view multi-component requests.
See RFE 92491 which addresses the concerns of those who closed this. I thought IBM was one organization and that the original RFE would have sufficed to get this functionality.
The closure seems to indicate that the reply came from the TSO ALLOC team.
Is there a reason this RFE could not have been passed to the appropriate team that is responsible for the dynamic allocation function to consider creating a text unit and thus provide the foundation to allow TSO ALLOC to support generations?
Please reopen this RFE and reassign.
A new text unit could be defined, but as this request is written multiple components will require update and this item is unlikely to be given high enough priority to be placed into the product plan. From a TSO/E standpoint, if the required function was available in the services currently being used, the request of TSO could be re-evaluated at that time.
So why can't there be a DSLMEMBR text unit for SVC 99?
The ALLOC command is designed as a user interface to SVC99 processing. There are no Text Units defined for specifying a generation number at this time. A Text Unit like DALMEMBR which is used for GDG datasets would need to be implemented for PDSE processing in SVC99 in order for us to consider implementation of this request.
This support should include the ability to allocate a new PDSE V2 with maxgens using the LIKE option (which currently ignores the V2 info and allocates a V1 PDSE).
Creating a new RFE based on Community RFE #89861 in product z/OS.