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
Created by Guest
Created on Sep 14, 2023

PDS with 4K directory blocks, Load module headers

Current PDS directories are 256 bytes with 8 byte key, so 38 blocks per 3390 track or 9.5K of data.  Allowing 4096 bytes with 8 byte key would allow 11 blocks per 3390 track or 44K of data.  

Current PDS directories only have full blocks until end of data, so adding or deleting a member name results in rewriting all block from point of change.  With a 4K block, you could default to using half a block, padding with low values, and after the last member name a high values entry.  When a block fills up (or empties), move entries to previous or next block to use half the total free space in each block.

Current load module header records allow blocking up to 256 bytes.  Blocking up to 4096 bytes would reduce the space needed for these records.

Current load module header records are very short and mixed in with object modules that have very large block sizes.  If header records were padded to 4K and object modules only used 4K blocks, then overwriting a deleted member with the same or fewer number of 4K blocks would be possible, instead of having to rewrite the entire library from the first unused area forward.

Idea priority Low
  • Guest
    Reply
    |
    Nov 6, 2023
    With the emphasis on clients using PDSE?s which offer additional benefits over PDS?s, this requirement is unlikely to be given high enough priority to be placed into the product plan. If this is still a priority for you, please open a new requirement.