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 250

API toolkit will not convert the Cobol fields into all upper-case.

Now, when importing Service interface from COBOL copybooks using the z/OS Connect Enterprise Edition (EE) API toolkit, it automatically converts the fields in COBOL copybooks into all upper-case. I would like it doesn't convert the COBOL fields in...
1 day ago in z/OS Connect 0 Submitted

Variable for specifying output length when creating copybook is not created

''- When creating a Cobol copybook with the current API specification file (json), a variable for specifying the output length is always created if it is a String.- When creating an outbound copybook, if you give the "characterWhiteSpace" option i...
4 days ago in z/OS Connect 0 Under review

Only one API can be re-executed in the zCEE server Refresh command

'- When the Refresh command is executed, all new deployment file APIs in the deployment path are refreshed.- When deploying a server, it is hoped that other APIs will not be affected (for HotDeploy purposes), but there is no function to refresh by...
4 days ago in z/OS Connect 0 Under review

Maintain variable names when importing copybooks from API Toolkit

'- When loading copybook from API Toolkit, the "-" (Dash) character is changed to "_" (Underbar). M/F standard variable name naming rules are different from the standardization issue and can become a point of failure due to developer's error. (ex)...
4 days ago in z/OS Connect 0 Under review

Support for multiple distribution paths

'- Supports only a single deployment directory per build file type for both inbound and outbound (ex) <WLP_USER_DIR>/servers/<serverName>/resources/zosconnect/services- It is impossible to separate folders by application code (customer...
4 days ago in z/OS Connect 0 Under review

for zOS Connect similar to ZCEE-I-160 we need the PATCH option for OAS2. We don't have the ability to run API 3.0 and our users are trying to access vendors that use PATCH.

So there are 3 HTTP methods that are not supported PATCH, TRACE, CONNECT. While TRACE and CONNECT are not that common in APIs, the PATCH HTTP method is more and more used. If only a set of values need to be updated, PATCH would be a more efficient...
about 1 month ago in z/OS Connect 0 Under review

Enable tracing per API on zOS Connect OAS 3

Given that when enabling tracing (either binary or non binary), there's an impact on server performance, that affects all APIs deployed on that server, we'd like to have an option to enable tracing per api, so that when analyzing we'll only be imp...
4 months ago in z/OS Connect 4 Not under consideration

z/OS Connect does not currently have a way to retrieve a list of the API requesters deployed in a server configured with OpenAPI3.

Currently, z/OS Connect EE provides functionality to list APIs, but it lacks a feature for listing API Requesters deployed on a z/OS Connect EE Server configured with OpenAPI 3. In contrast, with OpenAPI 2, API Requesters can be listed by sending ...
2 months ago in z/OS Connect 0 Planned for future release

Enhancing z/OS Connect for Dynamic API Integration with JSON Response Handling

Abstract This document proposes an enhancement to IBM z/OS Connect to support flexible consumption of API responses in JSON format without mandating COBOL copybook regeneration for every API update. This capability aims to streamline integration e...
about 1 month ago in z/OS Connect 0 Future consideration

Enable RACF passticket support for users creating API’s in Design Center to make calls to IMS.

Currently we are leveraging RACF Passticket support for many things within zCEE and it would be beneficial to have this capability for users who are creating API's in Design Center to make calls to IMS
about 2 months ago in z/OS Connect 0 Under review