Skip to Main Content
Cloud Platform

This is an IBM Automation portal for Cloud Platform 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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace WebSphere Liberty
Created by Guest
Created on Nov 27, 2021

Enhance liberty to recover from EDC5122I Input/output error. (errno2=0x12AA044F)

TCP socket the Liberty is listening on becomes unusable. This causes connection attempts to the Liberty server to fail. This can happen when the z/OS system is running in a CINET environment (to be able run multiple TCPIP stacks) versus an INET environment (where only 1 TCPIP stack can run) and the Liberty server is started after TCPIP is up, but before PAGENT is up (with AT-TLS). It can also happen if TCPIP is restarted.

When TCPIP initializes and AT-TLS is configured it will register to USS as a socket transport provider but does not send the final notification to USS until PAGENT starts and installs the AT-TLS policy definitions (and outputs message EZZ4250I). It is this final notification that causes USS to fail the accept call with the EIO if SO_EioIfNewTP has been set.

We found that Java always sets SO_EioIfNewTP in an CINET environment by design.

To recover from such EIO error, it becomes responsibility of the Liberty to restart the socket and automatically recover from this condition, rather than forcing the end user to recover it.

Our understanding is that some customers use CINET to separate internal and external IP traffic into different TCP/IP stacks.

We are aware that starting z/OSMF after all TCP/IP ingredients are active avoids the problem, however there is a catch. Our z/OS component has a function that does not require AT-TLS and works fine without it. Now we are providing new function which does require AT-TLS to be configured and running. Our concern is that customers that did not use AT-TLS will try our new function, will bring up AT-TLS and that will break the active z/OSMF server (that is based on the Liberty). It may seem a minor issue, but given the time it took to investigate the problem (original defect was open over 5 months before root cause was established, after collecting dozens of dumps and trace files), it could be frustrating for a customer.

Idea priority Medium
  • Guest
    Nov 30, 2021

    A support-pages document has been created describing this situation and two work-arounds.