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

LE

Showing 104 of 3362

C fopen() fails with errno 41 for VSAM VRRDS files; EDC5041I An error was detected at the system level when opening a file.

We have products that use the VSAM VRRDS file type. We would like to use Java and the JZOS Toolkit to open and read these files while remaining zIIP eligable. The JZOS Toolkit uses the C fopen() to open VSAM files and this fails for the VRRDS file...
over 7 years ago in z/OS / LE 1 Not under consideration

CEEDUMP truncated names of entry points

When forming CEEDUMP truncated the names of the entry points. Printed only the first 64 characters. CEEDUMP must contain a fully qualified entry point names.
almost 8 years ago in z/OS / LE 1 Future consideration

64-bit version of CEE3ERP required

CICS TS 4.2 and above provide support for Java by running a JVM within a 64-bit PIPI enclave (CELQPIPI). Every thread within the enclave begins life as an LE pthread and so has the LE ESTAE active for error handling. CICS enabled threads will addi...
about 9 years ago in z/OS / LE 2 Future consideration

bsearch library function for Metal C

Given the Metal C run-time library includes qsort, it should include bsearch
over 2 years ago in z/OS / LE 2 Future consideration

Provide option for open() and fopen() to set the CCSID of a newly created file

Support a new environment variable that would make LE's runtime open() and fopen() functionsset the attribute of a newly created file to a given CCSID. This environment variable could be named something like _EDC_NEW_FILE_CCSID. If set, for exampl...
almost 3 years ago in z/OS / LE 1 Not under consideration

Initialize DLLs upon program startup

All global variable initialization should happen for all DLL's that are implicitly loaded in an application before 'main' is invoked.
almost 4 years ago in z/OS / LE 0 Future consideration

Additional C functions for Linux portability

Add strnlen and wcsnlen (as on Linux) to the C runtime library.
about 4 years ago in z/OS / LE 0 Future consideration

Specify NONOVR for RUNOPTS at the application level

We would like a way to specify NONOVR at the application level (CELQUOPT CEEXOPT), similar to the region level https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.ceea500/clfdop64.htm#clfdop64Currently, the NONOVR/OVR are not...
about 4 years ago in z/OS / LE 2 Not under consideration

Provide an option to prevent RPTSTG(ON) from internally resetting the initial stack size

When RPTSTG(ON) option is set, LE resets the initial stack size to 1MB for 64-bit applications. This is fine for code in which LE automatically expands the stack when needed, however for generated code (as in JavaScript code from Node.js) in which...
about 4 years ago in z/OS / LE 2 Not under consideration

LE __heaprpt() that doesn't freeze all threads

We use the LE callable service __heaprpt() from C++ but it causes all threads to be frozen. Can we have a version that doesn't freeze threads (i.e from volatile fields in control blocks)? We don't mind if it's closely approximate.
almost 5 years ago in z/OS / LE 1 Future consideration