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 LE
Created by Guest
Created on Jun 26, 2018

Make CEETBCK statement_id parameter optional for performance reasons

In order to populate the statement_id parameter, CEETBCK needs to invoke the debug infrastructure, which can present considerable overhead if CEETBCK is frequently used ie. in non-error contexts.

Passing a null pointer (OMITTED in the case of COBOL) for the statement_id could be used as an indicator that the statement_id is not to be derived.

Idea priority Medium
  • Guest
    Reply
    |
    Mar 19, 2024

    We had issues with some Jobs, running hours than minutes (also on CPUTime), as it raises on every call to a submodule, an (internal) application error (and at last, ignores it). The (internal) error is managed by our error-handling, which called CEETBCK.

    As we changed from COBOL V4 to COBOL V6, we activated NOTEST(DWARF) to get more information on CEEDUMP. But just found out, CEETBCK needs alot more CPU.

    We don't need statement_id, so we would be very happy, if this idea is released.

    Thank you.

  • Guest
    Reply
    |
    Jun 27, 2018

    Would be helpful. The older CEETRCB is only there for compatibility reasons. CEETBCK is the recommended method, but at the moment with more overhead.