Skip to Main Content
Integration


This is an IBM Automation portal for Integration 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 Under review
Created by Guest
Created on Aug 24, 2026

Add error code to the output of the exception message from WMQ.common.services.trace

We are running MDBs on WAS for z/OS Liberty with MQ for z/OS.  We are conducting various testing and found Error code is missing in the output of the exception message from WMQ.common.services.trace. For example, IBM Documentation states that JMS Exception message of "Failed to reconnect one or more MDBs after a connection failure." has an error code of "MQJCA4014". However, actually, JOBLOG shows error code is missing as follows:

[8/20/26, 12:09:52:163 GMT] 000000b2 WMQ.commonservices.trace                                                                       
      I The connection factory property 'XMSC_WMQ_SSL_SOCKET_FACTORY' is not valid for a bindings mode connection to a queue manager.                                                                                                   [8/20/26, 12:09:52:166 GMT] 000000b2 WMQ.commonservices.trace                                                                       
      I ActivationSpec 'TestMDB1#TestMDB1.jar#TestMDB1' connect failed due to error 'JMSCMQ0001: IBM MQ call failed with compcode '2
' ('MQCC_FAILED') reason '2059' ('MQRC_Q_MGR_NOT_AVAILABLE').' (queue manager: 'M94A', host : 'localhost', port: '1414', channel: 'S
YSTEM.DEF.SVRCONN')                                                                                                                 
[8/20/26, 12:09:52:166 GMT] 000000b2 WMQ.commonservices.trace                                                                       
      I Failed to reconnect one or more MDBs after a connection failure.  

 

Error code is required to identify the message, and also if there is error code, it is possible to route the message to SYSLOG by specifying it in wtoMessage for JZOS function. This enables customer to monitor the message by automation products, such as NetView. This is very important to monitor the message and recovery the situation in mission critical online system. Currently we miss the message which is not allowed for the operation in mission critical online system.

Idea priority Medium