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.
The z/OS C library has poor support for PDS and PDS/E.
Specifically, when using fopen() to read or write members, there are no facilities to:
1) obtain existing user directory entry info (read and write)
2) update user directory info (write)
3) support for DISP=SHR plus ISPF Enqueue serialization
The first two of these cannot be easily worked around by user code without completely abandoning the use of the C-library for I/O.
Idea priority | High |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Don't forget to include support for PDSE Member Generations.
I believe this also limits the use of "/bin/cp any.file "//PREFIX.PDS(MEMBER)" when a SHR
allocation for "PREFIX.PDS" exists. That's often been a nuisance to me. /bin/cp should
employ SPFEDIT-style serialization for PDS members.
Thsnks,
gil
Creating a new RFE based on Community RFE #80811 in product z/OS.