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.
Answering:
- Each member can have a different number of generations. How would you count number of generations? Do you count all together or use another method? What is the value of having this count? The datasets MAXGEN is all that is required - the information on the individual member generations is not necessary.
- If a count for each member is being requested then it will not be implemented because LISTDSI works at the dataset level. A count of the number of actual generations would be helpful and yes that would require counting all generations within the PDSE which is probably overkill.
.Changing status to Uncommitted Candidate. Support would require support from RFE 107052.
For LISTDSI purposes the MAXGEN info for the PDSE would suffice and be easy to provide.
As a stretch along with SYSMEMBERS you could provide a count of the number of member generations in the PDSE.
For example:
SYSDSNAME: TEST.PDSE
SYSMEMBERS: 10 (total number of members - gen 0)
SYSMGENS: 45 (total number of member generations currently in use - gen 1 to n)
SYSMAXGENS: 20 (maxgens setting)
We have looked a bit more into this RFE and have some questions.
- Each member can have a different number of generations. How would you count number of generations? Do you count all together or use another method? What is the value of having this count?
- If a count for each member is being requested then it will not be implemented because LISTDSI works at the dataset level.