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.

ADD A NEW IDEA

My ideas: DFSMS VSAM

Showing 16

Remove requirement for SZERO=YES

When VSAM was first introduced, the only way, without requiring changes to every ATTACH in the address space, to share user storage was to use subpool zero. Sharing subpool zero has unintended consequences for a task that (ABENDed) ended without f...
11 months ago in z/OS / DFSMS VSAM 1 Future consideration

Espansion problem on DB2 table allocated on Storage group with available free space

DB2 for z/OS does not elect to reuse the space that it freed up on the first volume of multivolume vsam dat set.DFSMS will not and cannot know it is available for reuse.Since the data set is a Linear Data Set, it is up to the application to determ...
almost 8 years ago in z/OS / DFSMS VSAM 2 Not under consideration

Move CICS LSR Pools above the bar

This is in followup with RFE 114714 We would like to see the LSR pools moved above the bar for CICS. This will allow us to allocate more number of buffers which will reduce physical I/O
almost 6 years ago in z/OS / DFSMS VSAM 1 Future consideration

VSAM GSR support for encryption KEYLABEL

We have a VSAM application that uses GSR. If we attempt to establish an encryption KEYLABEL on the cluster the OPEN the fails with RC=166 along with IEC161I 121-163. We have a business and client need to be able to encrypt the DB using Pervasive E...
over 4 years ago in z/OS / DFSMS VSAM 3 Planned for future release

Improved support for SMB-related parms via DYNALLOC

We support customers who depend on the use of SMB and, specifically, SMBDFR=N. They have asked us to support continuous availability through the ability to detach & reattach certain VSAM files while the underlying platform (a started task) rem...
over 6 years ago in z/OS / DFSMS VSAM 2 Future consideration

Change Default For VSAM Files Definition Extent Constraint Removal To Yes

We experienced a major outage in a number of our critical production systems late last year due to a Db2 partition hitting max extents before it could hit the maximum defined data set size. Db2's space management algorithm was to scan the full dat...
over 1 year ago in z/OS / DFSMS VSAM 5 Future consideration

VSAM Verify to repair control blocks

If VSAM open feedback indicates improperly closed VSAM, we would like to have VSAM open to implicitly drive VSAM Verify one time and re-drive the open request. This is to be done in a fashion that application requesting OPEN is successful in the c...
over 1 year ago in z/OS / DFSMS VSAM 3 Not under consideration

Component name in IFGRPL

When the Vsam has no more volumes, there's a need to make an extent by idcams.To automate de idcams jcl, there's a requirement to know the component name of vsam to extent, but there's no information of that in ifgrpl. we need this information in ...
over 5 years ago in z/OS / DFSMS VSAM 2 Not under consideration

Increase the number of jobs that can be traced via an IDAVDTxx parmlib trace request

During a VSAM case TS004219577 I had to run multiple VSAM traces to collect trace entries for seperate address spaces, due to the IDAVDT00 parmlib entry being unable to support more than one job in the jobname parameter. If this were increased to ...
about 4 years ago in z/OS / DFSMS VSAM 0 Future consideration

Move the LSRPOOL Buffers to Above-the-Bar Storage

Move the LSRPOOL buffers from extended above the line storage to above-the-bar storage.
over 7 years ago in z/OS / DFSMS VSAM 4 Not under consideration