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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace AIX
Created by Guest
Created on Jul 22, 2023

Improve errpt CORE_DUMP entries to refer back to executable image that was running

When using dbx to analyze a core file that was dumped, the executable binary that was running must be used in combination with the core file to identify the exact instruction that caused the core dump.  In the errpt CORE_DUMP entry there is the full pathname of the core file and entries named "FILE SYSTEM SERIAL NUMBER" and "INODE NUMBER".  Per the these are “Information on the current working directory of the process, such as FILE SYSTEM SERIAL NUMBER and INODE NUMBER when the process dumps the core.”  However, it makes much more sense if these values are references to the executable binary image that was running within the limits of how Unix executes a file.

When an executable is started the INODE on the FILE SYSTEM are linked to by the OS and that file mapped to memory (in read-only mode) and the execution of the binary started. If the directory entry to the executable file is removed or renamed, the link to the inode by the OS keeps the memory map valid. Consequently the FILE SYSTEM/INODE numbers are the only information that can be guaranteed to be valid after the executable starts. That is why they would be returned in the errpt in the CORE DUMP message, they are the only things that can be certain to be valid at the time of the issue that caused the core dump.

It should be noted that in AIX Core Dump Data Collection this indicates that for an errpt CORE_DUMP entry the INODE NUMBER is that of the executable that was running. Specifically they take the INODE NUMBER and run find with it to get the full path of the executable.

Idea priority Low