Skip to Main Content
IBM Power Ideas Portal


This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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 Functionality already exists
Workspace IBM i
Categories Performance Tools
Created by Guest
Created on Jun 28, 2024

Extend call stack entries in PEX file QAYPEIAD

To analyze heap issues on ILE C++ applications we use IBM i PEX with Event *ACTGRPHEAP. The current outfile QAYPEIAD have fields for a call stack up to 16 entries.

This is maybe enough for C programs but for C++ programs with a lot of functions and classes this is usually not enough.

Because of this limitation it is hard to find the cause of the heap memory leak.

Idea priority Medium
  • Guest
    Dec 9, 2025
    There is already enhancement that allows changing the starting stack position where the 16 stack entries get recorded. To use it, the internal type and subtype numbers that identify the event must be provided. A special override string is passed into the ADDPEXDFN command in the TEXT keyword.

    The example ADDPEXDFN string below illustrates how to do for the *ACTGRPHEAP event. It has a type number of 4 and a subtype number of 11. IBM Service can provide the type and subtype of other events.

    ADDPEXDFN DFN(ACTGRPHEAP) TYPE(*TRACE) JOB((*ALL *ALL)) TASK(*NONE)
    MAXSTG(100000) TRCTYPE(*SLTEVT) SLTEVT(*YES)
    STGEVT((*ACTGRPHEAP *NONE *FORMAT2)) TEXT('#T041109')

    The TEXT keyword is used to modify the recorded stack positions by specifying a series of strings, one for each event to be modified.

    Syntax: #Tttssvv #Tttssvv ...
    where:
    tt is the event type number in base 10 (if value is < 10 it must have a leading 0)
    ss is the event subtype number in base 10 (if value is < 10 it must have a leading 0)
    vv is the stack frame override in base 10 (if value is < 10 it must have a leading 0)

    Requirements:
    All numbers must be provided in base 10
    The event type and subtype must refer to an existing PEX event
    The event format must be *FORMAT2
    The stack frame override must be a value between 01 and 15
    If all of the above requirements are not met, no error message will be issued and no action will be taken for the specified event type & subtype.

    IBM Power Systems Development