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 Future consideration
Workspace z/OS
Created by Guest
Created on Dec 8, 2023

Provide common APIs in support of PDSE Member Generations - Part 2

See https://ibm-z-hardware-and-operating-systems.ideas.ibm.com/ideas/ZOS-I-3783 for part 1.

Given that PDSE member generations are supported by some, and growing, IBM elements, it only seems reasonable to make it easy.


Thus I'm rating this IDEA as HIGH, although URGENT wouild also be reasonable.


Why High? That depends - imho it is high as the alternative is for IBM, and ISVs, to reinvent the code for every product that will ever interact with PDSE member generations. Something I foresee being a requirement as more tools on the open side (e.g. dsfs, zoau, zowe, ...) interact more with z/OS PDSEs. Doing a member delete, for example, on a PDSE with member generations for example would work but may leave the non-zero generations as orphans and completely inaccessible while consuming space if the delete is done improperly.

If we can assume that PDSE member generations are useful and valued then access to them should be important and for IBM open tools, along with ISV and open-source tools, with the FAMS documentation that will be a 'challenge'.



Idea priority High
  • Guest
    Reply
    |
    Mar 27, 2024
    We agree these API's in support of PDSE Member Generations are useful and it's in our long-range plan, however we cannot commit to a time frame right now.
  • Guest
    Reply
    |
    Dec 11, 2023

    Another interface that would be very handy is the ability to change the maxgens defined for a PDSE. Increasing would be fine as a limitation.

  • Guest
    Reply
    |
    Dec 11, 2023

    It was suggested that I be more specific so let's try these interfaces

    1. Return a list of all members and generations with ISPF statistics and absolute generation information

    2. Read a specific member/generation using either absolute or relative generation

    3. Update a specific member/generation using either absolute or relative generation

    4. Delete an entire member or individual member/generation using either absolute or relative generation

    5. Each should support masking for member names

    Ideally these should be provided as generalized interfaces that can be called from REXX, Python, Perl, etc.