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.

ADD A NEW IDEA

DFSMS PDS/PDSE

Showing 23

support binder date for pdse member generations

a pdse member generation 0 one can see the binder date but with other generations (-1, -2 etc), this information is not available (using Data Set Commander)
2 months ago in z/OS / DFSMS PDS/PDSE 0 Under review

IEBCOPY PDSE Member Generations Unload

IEBCOPY supports the ability to unload/reload a PDS to/from a sequential dataset. This is very useful for backup and transport. With the new GENS=ALL support for PDSE member generations the user expects to be able to do the unload/reload for their...
almost 3 years ago in z/OS / DFSMS PDS/PDSE 0 Future consideration

Disallow edit/save of PDSE generated members

Provide the ability to disallow editing the non-zero PDSE member versions.
almost 3 years ago in z/OS / DFSMS PDS/PDSE 1 Future consideration

A full PDSE dataset should be able to delete members without needing additional DASD space

We currently have a large SMP/E SMPPTS PDSE dataset which is full on a volume with only 5 available cylinders. Attempts to delete a member from the PDSE result in a E37-04 abend because the system is trying to get an additional extent. The dataset...
8 months ago in z/OS / DFSMS PDS/PDSE 1 Planned for future release

Share PDSE cross sysplex

Enhancement of PDSEs to be able to be shared cross sysplex. Currently, PDSE could not be shared outside a SYSPLEX.
over 5 years ago in z/OS / DFSMS PDS/PDSE 2 Future consideration

Unable to delete member in PDSE 100% utilized

See: PMR
over 9 years ago in z/OS / DFSMS PDS/PDSE 2 Future consideration

IEBCOPY Site Default for GENS=ALL

IEBCOPY should have a site wide default (parmlib) for GENS=ALL
almost 3 years ago in z/OS / DFSMS PDS/PDSE 0 Future consideration

Request to add more flexibility to PDSE Member Generations

This is an enhancement suggestion for the next version of PDSE libraries. With PDSE V2, you can retain multiple generations of members. This feature may have been added to close one of the remaining PDSE functionality gaps compared to regular PDS ...
almost 4 years ago in z/OS / DFSMS PDS/PDSE 3 Future consideration

Provide A Command to Increase a PDSE V2 MAXGEN Value

When allocating a PDSE Version 2 Library one is required to specify a MAXGEN value that limits the number of Member Generations allowed within the PDSE. If the value is too small the user must either live with it, or recreate the PDSE in such as w...
about 4 years ago in z/OS / DFSMS PDS/PDSE 1 Future consideration

Avoid out of storage abends in LLA

LLA should not try to honor LLACOPY when there is not enough private memory available to do so. A better behavior would be to reject the LLACOPY and produce a proper CSV message to indicate this anomaly. Maybe it is possible to delay the LLACOPY t...
over 1 year ago in z/OS / DFSMS PDS/PDSE 0 Future consideration

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.