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 33

Add the capability of creating custom HTTP headers for API Requesters

Our web-proxy gateways and API registrars require additional custom headers. Since these headers aren’t required by our API Providers, they usually aren’t in the OAS3 doc. Examples of what we use are: ConsumerId, ContextId, RequestId, and x- Gatew...
about 1 month ago in z/OS Connect 0 Future consideration

Add caching capability for non-JWT style token

We are starting to utilise IMS and CICS as API requesters and we are considering the future performance of our infrastructure. We have a concern about our authentication pattern which we think will add overhead to our API requestor flow. The...
8 months ago in z/OS Connect 0 Future consideration

Need API Requester Project creation in IDz

The Service and API archive projects are created using the primary menu option, File, and selecting “z/OS Connect EE Service Project” or “z/OS Connect EE API Project” respectfully in IDz. Using these functions generates projects specially setup fo...
about 6 years ago in z/OS Connect 10 Future consideration

enable wildcards in policy condition values

We would like the ability to use wildcard characters within a policy condition for example: <conditions> <header name="imstran" value="TRAN%A" /> </conditions> Where % is a single character wild card. This would be beneficial for...
7 months ago in z/OS Connect 0 Future consideration

Add affected service and IMS system to IMS Service Provider error messages in z/OS Connect

As of today when an IMS transaction service in z/OS Connect runs into a problem because the invoked transaction abends, doesn't respond in time or is stopped respectively the transaction cannot be invoked because of unsufficient authorization, z/O...
7 months ago in z/OS Connect 1 Future consideration

Override ConnectionRef in .ara file to address multiple RESTFul endpoints

API Requester scenario. 2 different environments , SVIL1 and SVIL2, sharing the same ZCNEE instance. There are 2 RESTful endpoints, one for SVIL1 and one for SVIL2 (they can also be API managers, like APIConnect) The same CICS program is deployed ...
almost 6 years ago in z/OS Connect 1 Future consideration

Add support for the HTTP method PATCH in API requester

As of z/OS Connect EE v3.0.9, the API requester function only supports 6 HTTP methods: GET, POST, PUT, DELETE, HEAD and OPTIONS. So there are 3 HTTP methods that are not supported PATCH, TRACE, CONNECT. While TRACE and CONNECT are not that common ...
almost 6 years ago in z/OS Connect 1 Future consideration

In OAS3, we still need a method to develop services using program communication areas to generate services from existing processes

The yaml OAS3 input document is not something most mainframe developers would have knowledge of how to develop correctly. However, they know how existing process and programs are working. Since a significant use of z/OS Connect is to expose access...
about 1 year ago in z/OS Connect 0 Future consideration

Remove empty fields from API responses

In the OpenAPI3 z/OS Connect Designer, there is currently no way to remove empty fields (i.e. "abcd" : "") from the API response. The OpenAPI2 API toolkit allowed us to easily do this. It would be beneficial performance wise to remove such fields ...
almost 2 years ago in z/OS Connect 0 Future consideration

SMF123 enhancement - error from server or HTTP response code mapping

Problem statement : Despite 'polite' requests to the contrary we have a few internal customers who employ HTTP status code's 500 in their HTTP status code mapping. In the event of transient issues in Open LIberty, it is not possible to establish w...
11 months ago in z/OS Connect 1 Future consideration