Skip to Main Content
IBM Power 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:

Post your ideas

Start by posting ideas and requests to this portal to enhance a Power product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas and add comments to ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The Power teams will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Specific link you will want to bookmark for future use

IBM Unified Ideas Portal - - Use this site to create or search for existing Ideas across all IBM products that are outside of Power, and track all of your personal interactions with all 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