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 Future consideration
Workspace z/OS Connect
Created by Guest
Created on Dec 11, 2025

Expand the granularity of the PreSor and PostSor times to be able to determine where in the z/OS Connect process slow response times are actually occurring

Due to a recent issue we had with a single API in API Provider where we were seeing intermittent very long PostSOR times for the same input client request data which was returning a relatively large response data structure from the SOR whilst other APIs were processing normally with no apparent CPU capacity or Heap issues in the server. We were unable to determine whether the large PostSOR time was due to:-

The amount of time taken for the response from the SOR to be returned into z/OS Connect. 
The amount of time taken for the response data structure to be transformed into JSON objects. 
The amount of time taken for the response from z/OS Connect to be sent back to the client.

I would like to request that the PostSOR time (and ideally for the PreSor time also) be broken down further to be able to quickly determine in which z/OS Connect process the time was actually being spent to be able to identify the appropriate area to investigate quicker. These values should be displayed in the Omegamon/JVM (and WEBUI etc) and z/OS Connect SMF 123 records in addition to the existing PreSor and PostSor fields.

Idea priority High