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 Delivered
Created by Guest
Created on Nov 4, 2020

Extend the JZOS ZFile class to include "unlocked" versions of read and locate for VSAM files

We've been prototyping and performance testing Java's ability to access VSAM record-oriented or Key Sequenced Data Sets (KSDS) using the ZFile class and now, our own home-grown functions based on the XL C/C++Run-Time Library – in particular, the locate and read family of functions.

It's seems very clear from our results that the ZFile.locate and ZFile.read functions will not scale in a multi-threaded fashion, i.e., while they are thread-safe, the underlying flocate() and fread() C functions are still blocking (or otherwise spending an awful lot of time) on a mutex that protects the file descriptor. We were under the impression that if we opened and allocated (from a pool), a discrete file descriptor for each thread, the mutex check would be “fast” and we would be able to scale with multiple threads. This is not the case.

When we substitute the ZFile locate and read methods with our own KSDS random reader based on the flocate_unlocked() and fread_unlocked() variants, we see good, near-perfect linear scaling. To preserve thread-safety, we continue to allocate a discrete, open file descriptor from a pool to each thread prior to performing the VSAM lookup.

Idea priority High
  • Guest
    Reply
    |
    Aug 1, 2022
    .Two new APIs, locate_unlocked and read_unlocked, have been delivered in:
    -SDK80 SR6 FP35 version of IBM SDK for z/OS, Java Technology Edition, Version 8
    -GA version (11.0.0.0) Semeru Runtime Certified Edition for z/OS, Version 11.0.
  • Guest
    Reply
    |
    Nov 4, 2020

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - z Systems Software
    Product - JAVA
    Component - JAVA
    Operating system - IBM z/OS
    Source - None

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - Programming Languages
    Product - C/C++ Compilers
    Component - Miscellaneous
    Operating system - IBM z/OS
    Source - None