Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. 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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Categories z/TPF
Created by Guest
Created on Apr 10, 2024

Please add the resolved queue name and MQ reason text to the BEVA0015E message

The use of the term "Transmit Queue" in Online Message BEVA0015E is misleading and derails operations staff troubleshooting. In the MQ Vernacular "Transmit Queue" is a special Queue associated with an MQ Sender Channel.

For Error Message BEVA0015E it would be more appropriate to look up the queue type and resolved queue name for "tqname" e.g. QUEUE BFE.DATA.EVENT.1G.PERF.A and display "ON LOCAL QUEUE", "ON REMOTE QUEUE", or "ON ALIAS QUEUE".  NOTE: the resolved queue name could be TO2 or MQDR and could be Local Queue or Remote Queue (with RName remote name).

Also, it would be of great assistance to look up REASON CODE e.g. 2030 in a MQRC_Lookup_table similar to the one in qmqz04 and add it to the display "MSG TOO BIG FOR Q"

BEVA0015E 14.33.11 BUSINESS EVENT PROCESSING WAS UNABLE TO TRANSMIT DATA FOR EVENT BFEde_1G.
09:33:12-ON TRANSMIT QUEUE BFE.DATA.EVENT.1G.PERF.A
09:33:12-WITH DISPATCH ADAPTER BFEda_1G_PF.
09:33:12-REASON CODE 2030.+

Suggested:
BEVA0015E 14.33.11 BUSINESS EVENT PROCESSING WAS UNABLE TO TRANSMIT DATA FOR EVENT BFEde_1G.
09:33:12-ON LOCAL QUEUE BFE.DATA.EVENT.1G.PERF.A
09:33:12-WITH DISPATCH ADAPTER BFEda_1G_PF.
09:33:12-REASON CODE 2030 MSG TOO BIG FOR Q.+

Idea priority High