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 Under review
Categories z/TPF
Created by Guest
Created on Jul 12, 2024

Improve performance of C++ try/catch when exception is thrown

Our coding best practice guidelines advise developers not to use the try-throw-catch method in C++ code for control of the program flow or transaction validation as the underlying TPF mechanism for identifying the source of the thrower results in a noticeable CPU overhead. The technique is reserved for throwing systemic errors, but these guidelines are impossible to enforce, and we still see examples of code that should use if/else or switch/case logic instead.

TPF identifies the address of the thrown exception using a sequential search to match it against addresses in CPS0 link map and the program IPAT and this causes the unwanted CPU overhead.

Suggestion here is to modify that exception address search by first checking the IPAT slot of the current program before embarking on the full sequential search of system tables, judging from our code base this would catch most instances of these exceptions without incurring the CPU overhead of an IPAT search.

Idea priority Low