Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software 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 (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 Not under consideration
Categories Runtime
Created by Guest
Created on Aug 1, 2017

Create new web socket timeout attribute

Like to request a new web socket timeout attribute separate from the DTIMEOUT element. As described in a recent PMR from IBM the DTIMEOUT is designed to release dead locks from other resources. It spends a lot of time issuing automatic retries and only terminating a single task every 1/2 second.

Web socket calls should be treated differently since the resources are external from CICS and terminating a single task every 1/2 second doesn't free any resources that could be held by the active web socket task.

It would be preferred to have a separate WTIMEOUT attribute on URIMAP definition or TIMEOUT parameter on the WEB SEND/RECEIVE/CONVERSE commands to provide the ability to timeout web socket requests immediately and return to the task so the developer can evaluate if they want to retry the connection and service request. No retries should be performed and should not have to wait for a large list of active tasks to be terminated in 1/2 second intervals which could lead to a long timeout duration.

Idea priority Medium
  • Guest
    Reply
    |
    May 22, 2018

    We have assessed this requirement. We have no current plans for this to be implemented and so this requirement is being declined at this point. The requirement will be kept in the RFE system and might be reassessed in the future. You also have an opportunity to resubmit in twelve months time if you wish it to be reconsidered then.

  • Guest
    Reply
    |
    Aug 7, 2017

    A limitation of RTIMOUT is that it is set at transaction level and therefore applies to all WEB CONVERSE/RECEIVE commands issued under that transaction. However, a single transaction may issue calls to say 2 or 3 endpoints, and each endpoint may have a different acceptable response time; but the single value of RTIMOUT will apply to each call. Adding a timeout() parm to the CONVERSE/RECEIVE commands would allow timeout thresholds to be tailored appropriately for each endpoint.

  • Guest
    Reply
    |
    Aug 3, 2017

    We are struggling with the send requests and could use a better mechanism to terminate the SEND's after a small wait.

  • Guest
    Reply
    |
    Aug 2, 2017

    We already have RTIMOUT for this purpose, it's documented to apply to WEB CONVERSE/RECEIVE commands. PIPELINEs also have their RESPWAIT mechanism which is also configurable for INVOKE commands. Are those existing mechanisms sufficient?