Skip to Main Content

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 (

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 Future consideration
Created by Guest
Created on Feb 20, 2017
Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit MESNS-I-183 Authentication Events.

Need to improve CHLAUTH logging on MQ for z/OS Merged

Our security policies dictate that we have to keep track of all the connection attempts.

So, before thinking of using CHLAUTH to secure our connections, we need CHLAUTH to use a separate log file (not MSTR or CHIN syslogs) to carefully log the following items for ALL the connections attempts:
• The date and time of the attempt;
• If the connection was granted or denied, or if it failed for any other reason;
• In case of denial or failure, an indication of what went wrong (unknown UserID, failed authentication, bad PW, expired PW, etc.);
• The Client UserID that was used;
• The MCA UserID;
• The server name (or hostname) targeted by the client;
• The queue manager name targeted by the client;
• The channel name used for this attempt;
• The IP address from which the attempt was made.

Idea priority High
RFE ID 101296
RFE Duplicate of 144378
RFE Product IBM MQ
  • Guest
    Oct 19, 2020

    This RFE has been closed as a duplicate of RFE 144378 (see

  • Guest
    Mar 14, 2017

    Adding more logging of connection information to MQ is something we are considering for a future enhancement.