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

Core Infrastructure

Showing 1550

Add IPv6 support to XTI API running in a language environment

We need to have IPv6 support for XTI C API running under a language environment. currently t_* calls support only IPv4.
over 6 years ago in z/OS / LE 1 Future consideration

Support Symbols LogDD also in DD:SYSTSIN

Hello, If using symbol logging combined with DD SYSTSIN in Tso-batch job //SYSTSIN DD *,SYMBOLS(xxxx,logdd)... then Loggdd is ignored now (as mentioned in JCL Reference) OA53706 does some changes in jes2 code that may support logging in this case ...
over 6 years ago in z/OS / JES2 2 Future consideration

64-bit support for CEE3LNG

CEE3LNG doesn't have 64-bit support.
almost 7 years ago in z/OS / LE 0 Future consideration

Add Support for RFC 3522 - Unnecessary Loss Recovery

The Eifel detection algorithm (RFC 3522) allows a TCP sender to detect a posteriori whether it has entered loss recovery unnecessarily.
almost 7 years ago in z/OS / Communications Server 1 Future consideration

For RRS_DELAYED_TRANSACTIONS Check, give customers ability to adjust transaction duration time

After activating RRS Healthchecker check RRS_DELAYED_TRANSACTIONS in z/OS 2.2, we encountered many instances of the check flagging exceptions, but the next interval the check runs, it is successful. Since the exception is only for one interval, it...
about 7 years ago in z/OS / BCP_RRS 1 Future consideration

Attaching 64 bit executable and passing parameters and env variables

In our 32 bit application we used an ATTACH macro to create a process and:- share subpools 0 and 1 (used macro paramaters SZERO=YES,SHSPV=1)- pass a list of arguments- pass a list of env variables However when we started attaching 64 bit executabl...
about 7 years ago in z/OS / LE 1 Future consideration

Granularity in defining volumes to be for hyperswap within a priceplex

Requirement for the capability of selecting specific volumes not to be taken into account by hyperswap (basic hyperswap / TPC/R) This could be done, for example, by creating a specific attribute in the dasd volume definition
about 8 years ago in z/OS / BCP_IOS 1 Future consideration

Provide LE Runtime Option to Defer CICS Program Releases

We use native language calls between our LE modules. Every call results in an EXEC CICS LOAD command followed by a branch. When the enclave terminates, LE issues one EXEC CICS RELEASE for every loaded program each time it was loaded. This results ...
about 8 years ago in z/OS / LE 2 Future consideration

Missing setsockopt TCP_KEEPALIVE constant and doc

1) TCP_KEEPALIVE is documented in Comm Svr pubs, but not in the C/C++ LIbrary Reference. 2) The constant TCP_KEEPALIVE is not defined in the header files
about 8 years ago in z/OS / LE 1 Future consideration

NULLIFY(RETENTION) misleading

Issuing a NULLIFY(RETENTION) returns with a IDC0531I ENTRY SYS1.UADS ALTERED, regardless of whether this is a nonSMS file or if there is no retention period specified. Neither is the DSCB information updated - only the catalog entry seems to be ch...
almost 9 years ago in z/OS / DFSMS Access Methods Non-Vsam 1 Future consideration