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.

ADD A NEW IDEA

z/OS Connect

Showing 249 of 8829

Enhance API Requester resilience

To improve API Requester resilence with a tactic similar to Circuit Breaker pattern
over 5 years ago in z/OS Connect 2 Not under consideration

API Requester Security flow jwt-bearer

With the two OAuth flows supported today by z/OS Connect: Client credentials (client_id + client_secret) Resource owner password credentials (client_id + client_secret + username + password) If we want to call a remote API from a mainframe applica...
over 2 years ago in z/OS Connect 0 Future consideration

Provide meaningful error messages for z/OS Connect and API toolkit problems

Currently z/OS Connect provides for a lot of configuration errors, RACF and Unix System Services problems neither an error message in the JES Job Log nor an error message in the messages.log. Often the only way to get an impression of what may be ...
about 7 years ago in z/OS Connect 4 Not under consideration

z/OS Connect support for mutiple Single Sign On algorithms

Our enterprise single sign on capability can use one of two different algorithms. Unfortunately, z/OS Connect looks specifically for one or the other – not both. And this can then cause a failure when receiving one it does not expect. Our request ...
6 months ago in z/OS Connect 1 Not under consideration

Health checker for z/OS Connect Endpoints

Health checker for z/OS Connect Endpoints.
about 5 years ago in z/OS Connect 2 Not under consideration

Support for IMS transaction name length required

Our site uses variable length IMS transaction names.The current implementation of the API Toolkit with fix PH09920 allows to specify a transaction name that will either be padded with spaces for a maximum length of 8 characters or if the Space Del...
about 3 years ago in z/OS Connect 3 Not under consideration

zOS Connect enable generics in zosConnectAPI name construct

in order to secure API using the authorizationInterceptor for access by different teams we currently have to specify every API and define the relevant access. With naming standards we can group these much more efficiently using generics for exampl...
about 6 years ago in z/OS Connect 4 Not under consideration

z/OS Connect to support the token being returned from the authorization server in a custom field in an OAuth 2.0 flow

We are using the z/OS Connect OAuth 2.0 support to obtain an access token from our EUA Authorization server. This retrieves the access token from the “access_token” field of the JSON response, as per the OAuth 2.0 specification. In the response th...
over 1 year ago in z/OS Connect 0 Future consideration

z/OS Connect Field/Header Validation

Provide basic validation for input API fields.
over 3 years ago in z/OS Connect 2 Not under consideration

Possibility to parameter specific TimeOut by API

Now, ZCEE provides a asyncRequestTimeout parameter which allows to limit the request time for all the API in the server. However, it would be useful to be able to manage exception on an API basis.
almost 5 years ago in z/OS Connect 1 Not under consideration