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 Aug 15, 2023

if user sign-on to the queue manager fails we see the RACF-Message, but there exists no correponding massage which can identify the Channel or IP-Adress of the causer

in our case a srvconn tried to logon with an userid ‚admin‘ which does not exists in RACF. This happens automaticaly several times at a minute and made our joblog  unreadable with mass of ICH408I messages. We did not find the causer of this problem because it exists no corresponding CSQ-Message where we can identify channel name or the IP-Adress.   We need a message like CSQX790I (may be with IP-Adress or Channel name). This message will be reported in the CHIN logs if the connection authentication fails for a user due to CHLAUTH. 

Idea priority High
  • Guest
    Jun 13, 2024

    Same for us here.
    We strongly recommend a channel (and IP-Address).

  • Admin
    Matthew Leming
    Dec 12, 2023

    We agree this would be useful to have in the product.

  • Guest
    Sep 28, 2023

    I agree to this IDEAD as for every error message it is important to be able to detect the root cause of it and it is even more important for security related messages.