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 Delivered
Categories Runtime
Created by Guest
Created on Nov 8, 2012

Timeout for SOCKETCLOSE in TCPIPSERVICE for the first request

The TCPIPSERVICE attribute called SOCKETCLOSE does not allow to specify a timeout value for the first time request. And the first request is in fact the most interesting one to set up a parameter for timeout. The description of the attribute in the Infocenter of 4.2 is:

SOCKETCLOSE({NO|hhmmss})
Specifies if, and for how long, CICS should wait before closing the socket. The SOCKETCLOSE attribute does not apply to the first receive request issued after a connection is made. On the first receive request, for the HTTP, USER, and ECI protocols, CICS waits for data for 30 seconds before closing the socket. For the IIOP protocol, CICS waits indefinitely.

We would request an enhancement to allow to configure a value for the timeout in the case of the first request.

Idea priority High
  • Guest
    Reply
    |
    Aug 18, 2016

    This has been addressed by APAR PI39026 for CICS TS 4.2 and PI31452 for CICS TS V5 The APAR fix allows the initial wait to be configured via the DTIMOUT setting for the transaction specified on the TCPIPSERVICE (i.e. CWXN or another transaction that runs DFHWBXN - CWXN will be needed in this case because the data isn't already available). It can be configured on a TCPIPSERVICE basis by creating a different transaction with the required DTIMOUT.

  • Guest
    Reply
    |
    Oct 5, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Transaction Processing
    Product - CICS Transaction Server

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Transaction Processing
    Product - CICS Transaction Server

  • Guest
    Reply
    |
    Dec 5, 2012

    This will be considered for inclusion in a future release.