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.

Status Future consideration
Workspace z/VM
Created by Guest
Created on May 20, 2022

Implement the existing, but not yet supported, TLStimeout parameter for IUCV IOCTL socket calls

When using IUCV IOCTL calls, in particular SIOCSECCLIENT and SIOCSECSERVER to secure an established socket connection, I have seen cases where the call sits indefinitely with no response or failure. Because the documented TLStimeout has not been implemented yet, the call hangs indefinitely waiting for completion or a failure ... there is no other documented method to cleanly "cancel" the call to secure the socket. Because these calls may go "off platform", it seems various anomalies in the network can result in this situation where the IOCTL call neither completes, nor fails, and thus just hangs indefinitely.
Idea priority Medium
  • Guest
    Reply
    |
    Dec 1, 2022

    This option looks critical in some situation, otherwise EXECs and following processes hung. We experienced this situation recently and are not happy with missing TLS timeout option.

  • Guest
    Reply
    |
    May 26, 2022

    Seems necessary

  • Guest
    Reply
    |
    May 24, 2022

    This has caused a serious problem for us. If the socket never terminates, the logon process will hang until VMSECURE is recycled. We have about 30 z/VM lpars and cycling vmsecure on each one is not exactly graceful way to circumvent this issue. This also includes production systems. It's a problem that really does need to be addressed.