Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. 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
Created by Guest
Created on May 15, 2025

zFile API write-lock on VSAM at record level for high concurrent VSAM write access to different records

Our product (zExplorer server on z/OS) is using VSAM for book-keeping our metadata of dataset ENQ. The VSAM needs to support high level of concurrent of write (and read) access from different users, servers from different sysplex VMs, to different (in most cases) or same records.

Currently zFile API for VSAM has locking done at VSAM level, causing a race contention for the concurrent write attempts due to exclusive locking attempt per write. It's helpful if the locking could be done at record level, so the contention could be improved especially for concurrent writes to different records.

There is a reference of Record Level Sharing VSAM feature that may be related to our requirement https://www.ibm.com/docs/en/zos/2.4.0?topic=sharing-vsam-record-level

Thank you.

Idea priority Medium
  • Guest
    Aug 7, 2025
    .ZFile allows access to use RLS via the mode string. Otherwise it is outside the scope of any product to control access to a data set on a record level other than DFSMS.