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 Delivered
Workspace z/OS
Created by Guest
Created on Dec 17, 2014

Make CONNECT timeout customizable

The standard sockets CONNECT call has a built-in timeout value of 3 minutes. This value is not customizable. Would like to allow this to be customizable based on user needs.

(Could not categorize this under Communications Server as there was no way to specify this as a component.)

Idea priority Medium
  • Guest
    Reply
    |
    Nov 19, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - z Systems Software
    Product - z/OS Communications Server

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Enterprise Networking
    Product - z/OS Communications Server

  • Guest
    Reply
    |
    Apr 10, 2015

    As stated in one of the comments above, we believe this requirement is addressed by function provided in z/OS V2R1 CS.

  • Guest
    Reply
    |
    Apr 2, 2015

    Please review the previous update and let us know whether the alternatives described meet your requirement. Thank you!

  • Guest
    Reply
    |
    Jan 6, 2015

    This feature is available in z/OS V2R1 Comm Server. Two new options (CONNECTTIMEOUT and CONNECTINITINTERVAL on TCPCONFIG statement) were introduced to allow customization of the TCP connection establishment timeout. The CONNECTTIMEOUT parameter allows you to specify the overall timeout value for connect processing. Also in this release the default timeout for connection establishment was reduced to 75 seconds from 3 minutes. Here's a link to the documentation of these new parameters:
    https://nsjazz.raleigh.ibm.com:8038/ccm/web/projects/RFE%20for%20ENS#action=com.ibm.team.workitem.viewWorkItem&id=31010

    Also note that an application using the sockets API can overide how long it waits for TCP connections to be established when it is acting as a client. Below are the steps that can be used to customize the timeout value on an application basis (the examples/references are for CICS sockets but these concepts apply to other socket APIs as well):

    1) To set a socket in non-blocking mode or blocking mode: Use FCNTL call. Alternatively can use IOCTL call for the same purpose. Note, the socket should be placed in non-blocking mode before issuing the CONNECT API. Here's a pointer to the z/OS V1R13 IP CICS Sockets publication that describes this API:
    http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/f1a1g170/8.6.6?SHELF=all13be9&DT=20100603025010
    2) Issue CONNECT call. The call will complete immediately with an ERRNO of 36 (EINPROGRESS). This indicates that the CONNECT has been scheduled. Here's pointer to the ERRNO descriptions:
    http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/f1a1g170/B.1?SHELF=all13be9&DT=20100603025010&CASE=
    3) Issue SELECT call, specifying the Write bit mask for the socket descriptor in question and specify a TIMEOUT value of how long you are willing to wait for completion of the connect. When SELECT returns, RETCODE indicates the result:
    > 0 - indicates the number of conditions (based on the input bit masks) that were met
    0 - No conditions met, the call timeout
    - 1 - An error occured (ERRNO reflects the error).
    Documentation for SELECT:
    http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/f1a1g170/8.6.30?SHELF=all13be9&DT=20100603025010
    Note, manipulating bit strings can be complicated in COBOL. As a result some helper routines are provided, see EZACIC06 program:
    http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/f1a1g170/8.7.5?SHELF=all13be9&DT=20100603025010
    Finally, we do provide some sample code in the manual for a COBOL program invoking SELECTEX (variation of SELECT). See the following link:
    http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/f1a1g170/E.7?SHELF=all13be9&DT=20100603025010
    4) After the select is completed, need to ensure that the socket is turned back into blocking mode if that is what the remaining code expects (using the FCNTL call above). Or if you stay in non-blocking mode, then you would need to make use of SELECT to determine when it is time to read from the socket, etc.

    Does this information satisfy your request? If not, can you clarify what is missing? Thanks!

  • Guest
    Reply
    |
    Dec 29, 2014

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Enterprise Networking
    Product - z/OS Communications Server
    Component - TCP/IP
    Operating system - IBM z/OS

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - zSeries Software
    Product - z/OS
    Component - Other
    Operating system - IBM z/OS

  • Guest
    Reply
    |
    Dec 18, 2014

    Creating a new RFE based on Community RFE #63590 in product z/OS.