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 243

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...
8 months ago in z/OS Connect 0 Future consideration

Provide API Name in addition to field name for GMOMW0005E / GMOMW0021E error in zOS Connect

Currently we are debugging a lot of GMOMW0005E errors and they only provide the field name that encountered the error. Initially these were easy to debug but now that the environment is growing at a rapid pace it is near impossible as the error on...
over 3 years ago in z/OS Connect 1 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 ...
3 months ago in z/OS Connect 1 Not under consideration

z/OS Connect EE - Allow enablement of TRACE at individual API provider/requester level

To capture TRACE on-demand, Today it is possible only to enable at Server instance level. In Larger Enterprises z/OS Connect EE is utilized as a Shared entity in a SYSPLEX which can be shared my many applications. So, to trace a particular applica...
over 4 years ago in z/OS Connect 6 Not under consideration

Validation of API Provider requests against the OpenAPI 3 specification

Enable validation of API Provider requests against the OpenAPI 3 specification. Since this will have a performance overhead, it should be fully configurable.
almost 4 years ago in z/OS Connect 2 Not under consideration

Allow API/SAR Deployment to specified Folder Location

Related to RFE 112082, We envision the Eclipse API toolkit having a pop-up providing an option to specify a location when doing a deploy. It is important that our application developers for each of our lines of business to choose their separate LO...
almost 7 years ago in z/OS Connect 4 Not under consideration

z/OS Connect should provide appropriate HTTP error codes on errors within z/OS Connect or backend systems

Since a short time it is now possible to define HTTP return codes in z/OS Connect depending on codes the application sends back its response message, but in error Scenarios z/OS Connect still doesn't provide an appropriate HTTP error code. Instead...
almost 6 years ago in z/OS Connect 7 Not under 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 ...
over 2 years ago in z/OS Connect 0 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...
over 1 year ago in z/OS Connect 0 Future consideration

Allow larger variable length fields beyond the current limit of 32767

We’re proposing an enhancement to z/OS Connect’s OPENAPI2 to better handle larger variable length fields. Currently, to accommodate large data returned by our apiRequester endpoint, we’re required to set the varying field to a fixed length (charac...
7 months ago in z/OS Connect 0 Future consideration

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.