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
Created by Guest
Created on Apr 22, 2025

In OMEGATOM v5.6, desire the history panel average response time to have the ability to exclude (filter out) transactions

The solution to recent tickets TS017091419 & TS017972601 where a long running transaction CSOL was being included in the average response time, was to use parameters and filters on service classes to include all transactions but CSOL.  Desire the ability to specifically exclude this transaction, rather than include all BUT this transaction.

It took many months (over 8 months) to arrive at the solution for the issue and it is very cumbersome.  There are multiple filters involved, and the service class will need to be set up for all of the many CICIS regions.  It would be much easier to set up, use, and maintain if we could exclude specifically what is not needed. 

In our environment there will be 300+ regions.  There are some caveats such as limit on number of characters for the filter, and that we have many transactions that will need to be understood/determined/researched in order to get all filtering the way we want it. 

We use the history panel to monitor our systems for high response time and we must be able to not have CSOL long running transaction in our results, because it is skewing our results.  So we must go through with the resolution above if that is our only option.  But would prefer another option.

Idea priority Medium