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

support for 'scopes' as available in OAUTH2.0 standard

z/OS Connect Enterprise Edition currently supports OAUTH access_token to authenticate a requester, but it doesn't support 'scope' to authorise a request. The https://tools.ietf.org/html/rfc6749#section-3.3 explains about scopes.With help of 'scope...
almost 4 years ago in z/OS Connect 1 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...
9 months 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...
about 1 year ago in z/OS Connect 0 Future consideration

Using specific CICS Channel Name

In the z/OS Connect OpenAPI3 Designer, "JSONCHANNEL" is always used as a CICS channel name and there is currently no way to change CICS channel name when we invoke CICS Channel program via z/OS Connect. It means if customer has CICS Channel progra...
almost 2 years ago in z/OS Connect 1 Future consideration

Update CICS Service Provider to produce connector statistics

We would like to be able to monitor the connection statistics for the CICS SOR backends and whilst the IMS provider does use JCA, the CICS provider does not and therefore no JCA MXBean is provided which would allow z/OS Connect to gather the stati...
over 2 years ago in z/OS Connect 0 Future consideration

Add the support of required field in APIS Body

We need to force APIs consummer to provide mandatory fields in the JSON body of an APIS.This is really important for APIS that use a MQ service because in this case we have no way to check fields before the message is PUT in the queue by the servi...
over 2 years ago in z/OS Connect 2 Future consideration

Add more options to Attribute characterWhiteSpace

Currently, the build toolkit properties file attribute characterWhiteSpace=COLLAPSE removes all leading, trailing, and embedded white space from type string fields. Furthermore, the same option replaces with single space characters all tabs, new l...
almost 3 years ago in z/OS Connect 1 Future consideration

MQ Provider should propagate client user Thread Identity via MQ to backend subsystems

The current API Provider / MQ-Provider should allow the current RACF Thread Identity to be passed via the MQ message to the backend MQ subsystem to allow the backend applications to execute that request using that same identity. This would then be...
over 3 years ago in z/OS Connect 0 Future consideration

REDEFINES Behavior: Requirement to support multiple redefinitions on input (request)

We are requesting support of JSON draft 4 schema within z/OS Connect, with "anyOf" & "oneOf" as it applies to REDEFINES support in IMS and CICS. Requirement: We have a requirement to support multiple redefinitions on input (request). The attac...
almost 8 years ago in z/OS Connect 3 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...
8 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.