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.

Status Planned for future release
Workspace z/OS Connect
Created by Guest
Created on Jun 7, 2018

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 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 alternative than PUT.

In z/OS Connect EE, when the communication stub sends a request with a PATCH method, the response from z/OS Connect EE is:
{"errorMessage":"BAQR1140E: Error occurred when z/OS Connect EE attempted to access a RESTful API.
Error: BAQR1140E: Error occurred when z/OS Connect EE attempted to access a RESTful API.
Error: The method PATCH is not supported by RestClient."}

JAX-RS 2.0 does not support PATCH, but JAX-RS 2.1 does. It would be great if z/OS Connect EE could rely on JAX-RS 2.1 and add support to PATCH (then the supported inbound and outbound HTTP methods would be the same).

Idea priority Medium
  • Admin
    Demelza Farrer
    Reply
    |
    Jun 27, 2024

    This IDEA has been further assessed by the team and is now "planned for future release".



  • Guest
    Reply
    |
    Jul 23, 2018

    Whilst this requirement is valid, based on our current plans and priorities for IBM z/OS Connect Enterprise Edition, it is not likely that this could be implemented in the next 12 months. Correspondingly this requirement is being declined at this point. The requirement will be kept in the RFE system and might be reassessed in the future. You also have an opportunity to resubmit in twelve months time if you wish it to be reconsidered then.

30 MERGED

HTTP PATCH method support in zOS Connect

Merged
Under the current version of z/OS Connect, in the API Requester scenario, if the consumed service exposes an API through the HTTP PATCH method, the build toolkit fails.
almost 6 years ago in z/OS Connect 1 Planned for future release