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 Apr 27, 2022

Change QMHRCVM, QGYOLMSG and MESSAGE_QUEUE_INFO to return the same severity for immediate messages

Today the QMHRCVM API returns 0 (zero) for messages send by the SNDMSG command, whereas DSPMSG, the QGYOLMSG API and the MESSAGE_QUEUE_INFO SQL table function return 80. That is confusing, for example when using both APIs.

From the documentation of the QMHRCVM API:

Message severity. The severity of the message received. Possible values are 0 through 99. If the message being received is an immediate message, the message severity is not returned.

Following the API documentation it seems, that there is a bug in the QGYOLMSG API (and maybe because of that in the MESSAGE_QUEUE_INFO SQL table function and DSPMSG).

Please fix that to ensure consistent information.

Idea priority High
  • Guest
    Jun 1, 2022

    Thank you very much for the additional information regarding the severities assigned by the system and the usage of the APIs. However that does not explain why RCVMSG and QMHRCVM do not return the message severity. I already opened a PMR (TS009151987) for that and I was told that that works as designed and that I could (or should) open a new idea.

  • Guest
    May 31, 2022
    When sending an immediate (impromptu) message, the following severity is assigned by the system:
    80 ??? Information
    99 ??? Inquiry, Sender copy, Reply
    0 ??? all other message types

    When displaying an immediate message, (ie. DSPMSG command, QGYOLMSG API) the message severity is shown/returned.

    When receiving an immediate message (ie. RCVMSG command, QMHRCVM API) the message severity is not returned.

    MESSAGE_QUEUE_INFO uses the QGYOLMSG API, therefore it will return the message severity for immediate messages.

    IBM Power Systems Development