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 Not under consideration
Workspace IBM i
Created by Guest
Created on Nov 9, 2023

Include the Message File and library in the QUSEC (ERRC0100 or ERRC0200) when returning messages from APIs

Today, when the QUSEC struct is passed to an API, the MSGID and MSGDTA values are returned. However the Message File from which the message was retrieved/sent is not provided. This causes an issue with messages such as GUI0002 or SQLxxxx that do not exist in QCPFMSG message file. Perhaps a new ERRC0300 format option is needed that will include the message file from which the MSGID was sent. 

We need this in order to log the message either to the joblog or another msgq of our choosing via the sndmsg interfaces. For example, I call QMHRTVM or QGYOLJOB or similar and it fails with GUI0002, it is not in QCPFMSG and hence I cannot turn around and log that message to the joblog in its "normal" format  of
0 is not valid for length of receiver variable.

Instead I can only write something like "API QGYOLJOB returned GUI0002"

Please provide a way to retrieve the message file/library for the messages returned into this parameter/struct.

Idea priority High
  • Guest
    Jan 4, 2024
    Thank you for submitting your Idea to IBM. It is not likely that this suggestion will be implemented due to lower priority, therfore I am declining at this time.

    IBM Power systems development