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 108 of 3553

LE should give an error for an attempt to start a new enclave in a single-enclave environment

An LE environment that is set up for a single enclave only will not support an attempt to start a second enclave. Currently, if this is attempted in COBOL, the result is a S0C1 in CEEBPIRA. An APAR is open that will change this to be a U4093-92 ab...
over 3 years ago in z/OS / LE 1 Not under consideration

LE's Heap Latch should be FIFO, not LIFO

Serialization via LIFO has the negative effect of leaving the first task in to never obtain the resource when processing is very busy. FIFO allowed everyone the chance to get in and get out with little delays even during a busy time.
over 5 years ago in z/OS / LE 1 Future consideration

LE to surface correct information when 31/64 bit code is incorretly used via DLL

* if 31/64 bit code in intermixed in a non supported manner (DLL)* message "EDC5206S DLL module name too long" is shown * The correct information (CEE3587S A call was made to a function in the AMODE 31 DLL //FU018J from an AMODE 64 caller)surfaces...
about 8 years ago in z/OS / LE 1 Future consideration

Monitor the z/OS Language Environment Heap Usage

The usage/allocation of the LE Heap storage would affect the performance of the IBM CMOD product that is using it. In the reported case, when the LE Heap is not properly tuned, high CPU consumed by the CMOD address space is observed. Although the ...
almost 7 years ago in z/OS / LE 0 Future consideration

have CEEZ1IPT fail more gracefully

When an application is using PIPI, and the PIPI Main code creates children but then completes back to PIPI, future services that need the IPT will fail with an Abend0C4 in CEEZ1IPT due to not getting a CAA address from CEEARLU.CEEZ1IPT needs valid...
almost 4 years ago in z/OS / LE 0 Future consideration

Allow modification of CEEDUMP naming convention via parms

Currently, there is no means to change the CEEDUMP naming convention. The LE code uses /path/CEEDUMP.date.time.PID or /path/FNAME.date.time.PID, which may not match the convention a customer uses for other trace and dumps in Java. Providing such a...
about 5 years ago in z/OS / LE 2 Not under consideration

Callable Service for RFC 4122

UUID generation (similar to UUID@GEN in TCPIP SEZLOAD) should be available as a callable service to generate an RFC 4122 compliant unique user id.
about 10 years ago in z/OS / LE 2 Not under consideration

LE Load Notification User exit : Add RMODE indicator values to CEEFLG in CEELNUE csect

In the LE Load Notification User exit it would be very valuable to identify the RMODE of the program which caused the exit to be accessed. 24-bit and even 31-bit storage can be exhausted in environments with many architectural modules for IMS appl...
over 7 years ago in z/OS / LE 0 Future consideration

Allow disposition to be specified on fopen

DISP=SHR cannot be set when fopening a file in write mode. In read mode it defaults to DISP=SHR. If the file is a PDS(E) member, this locks out the whole PDS(E) so that no-one can browse the other members. If you use a DD Card, then you can specif...
over 4 years ago in z/OS / LE 3 Not under consideration

Support Posix semaphores

The Posix semaphore mechanism (defined by these APIs: sem_open/sem_close/sem_unlink/sem_trywait/sem_wait/sem_timedwait/sem_post/sem_init/sem_destroy/sem_getvalue) is an alternative to the XSI semaphore mechanism currently implemented in z/OS. Posi...
almost 6 years ago in z/OS / LE 3 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.