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/OS
Categories LDAP
Created by Guest
Created on Nov 20, 2020

Request to add timeout functionality to synchronous binds

Our client would like to put a timeout parameter in on the z/OS client side and are trying to understand if that's possible. They are using GLD.SGLDHDRC(LDAP) to compile their C routine and are wondering if there is anything equivalent to the LDAP_OPT_TIMEOUT and LDAP_OPT_NETWORK_TIMEOUT property fields.

Ldap_result() works with asynchronous LDAP ldap_simple_bind( ) call. The method uses a msgid to specify the message identifier assigned to the LDAP request. Currently they are using ldap_simple_bind_s( ) call, which is synchronous. They have concerns using an asynchronous bind and believe their application's bind calls are performing a cross forest authentication. If so, then this method will not work for them.

Their comment on the LDAP_OPT_TIMEOUT and LDAP_OPT_NETWORK_TIMEOUT properties:

Do you know why these two time out properties are not available in the LDAP system library on the mainframe:

GLD.SGLDHDRC, members LBER and LDAP:

ldap_set_option(connection, LDAP_OPT_TIMEOUT, (void *)&optTimeout)

ldap_set_option(connection,LDAP_OPT_NETWORK_TIMEOUT, (void *)&networkTimeout);

LDAP_OPT_TIMELIMIT is the only property that is available for them to use. But the other two time out related properties are closely related to the client side timeout, which is what they want to use. They have seen in online forums that they are available to Python, C, or Java versions of the code on other platforms.

Idea priority Medium