Skip to Main Content
IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. 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 Future consideration
Workspace z/OS
Categories z/OSMF
Created by Guest
Created on Jun 26, 2023

Option to allow z/OSMF dataset API to return error message rather then HTTP error response code

When we use a client to make numerous z/OSMF API dataset calls, if an error HTTP response code is returned, z/OSMF ( Liberty ) closes the established TCPIP connection.  This is expected Liberty behaviour as this conforms to the published open RFC standards.

However we are doing many such calls, and if we get a number of HTTP error response codes, the client has to re-establish the SSL/TLS connection to z/OSMF again, which takes time and CPU.

What we would like is to be able to add an option on the z/OSMF dataset API to tell z/OSMF that if there is an error, to return an ok HTTP 200 response code but also an error message indicating what the error is.  Then in our client we would scan for an error message and take action accordingly.  But this would let our client reuse that SSL/TLS connection again for another request.

This would improve the usage of z/OSMF for us in this use case and future DevOps initiatives.

Idea priority Medium