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 226

Support outbound CICS --> REST API (OpenAPI v3) calls using a containerized solution on OpenShift

Currently the exposure of OpenAPI 3 REST APIs inbound to z/OS is supported on openshift x86 containerized architecture. Outbound calls from CICS to the REST API (OpenAPI v3) instead require the runtime to be installed on z/OS. This generates a dup...
8 months 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

API Requester support for additional content-type

Currently, API Requester only supports a content-type of application/json We have teams that require to be able to call REST APIs with content-types other than the one currently supported:multipart/form-dataapplication/x-www-form-urlencodedapplica...
9 months ago in z/OS Connect 1 Not under consideration

Enable Passticket support in OAS3 Run-time

OAS2 Run-time for zOS Connect supports Passticket credentials. This same capability needs to be provided in OAS3 in all systems of record as it is in OAS2 Run-time
9 months ago in z/OS Connect 0 Planned for future release

Export 88 levels as JSON comments when building a Z/OS Connect API in Z/OS explorer

The 88 levels in a Cobol program and copybook contain very useful code that could very easily turn into comments when exporting. These comments would be helpful for downstream developers to know constraints on certain fields
10 months ago in z/OS Connect 0 Future 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...
10 months ago in z/OS Connect 0 Future consideration

Enable z/OS Connect API Requester Feature to Transparently handle API Endpoint changesEnable z/OS Connect API Requester Feature to Transparently handle API Endpoint changes

Enable z/OS Connect API Requester Feature to Transparently handle API Endpoint changesCurrently, when an API endpoint has new response fields added that an API Consumer does not need, z/OS Connect API Requester will start to fail unless its API Re...
10 months ago in z/OS Connect 1 Not under consideration

ADD the posbility to use Header in the oAUTH

z/OS Connect OAuth 2.0 support follows the The OAuth 2.0 Authorization Framework standard: https://www.rfc-editor.org/rfc/rfc6749fo . This does not specify any header than the Authorization header be flowed on the request. There is no way to confi...
11 months ago in z/OS Connect 1 Not under 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

Avoid API Request failures when the API request/response structure has non-breaking changes.

Context: We are using z/OS Connect's API requester function to make ReST API calls from COBOL Batch programs. We use the Swagger definition (Open API 2.0) of the API, to build the API requester artifacts (COBOL Copybooks and ARA package) via zconb...
12 months ago in z/OS Connect 1 Not under 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.