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 IBM i
Categories Core OS
Created by Guest
Created on Mar 31, 2020

Allow message overrides in all threads of a multi-threaded job

Currently the IBM i allows you to override database files and printer files that impact on ALL threads that run in a multi-threaded job. Message file overrides only override message file operations in the initial thread.

This limitation needs to be removed so that message file overrides have the same level of functionality as database and printer files.

Use Case:

Our software is primarily written in C/C++ and runs multi-threaded where applicable. We had a recent issue where a pointer was not set and message MCH3601 from QCPFMSG was issued. The information in the QPJOBLOG gave the failing statement but we needed a call stack to track where the function with the failing statement was called from, since it is a common routine in our code.

Advice from IBM was to change the severity of the message to 50, from 40, and to ensure that the DMPLST settings would provide a DSPJOB output.

Idea priority High