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 Not under consideration
Created by Guest
Created on Jan 17, 2024

Allow override of "StrictHostKeyChecking" in crtmqm

When creating an RDMQ queue manager, "StrictHostKeyChecking" is enforced when creating standby queue managers. Since this is hardcoded in the library and the ssh command line take priority, it's impossible to override. /usr/bin/ssh -o StrictHostKeyChecking=yes -o PasswordAuthentication=no -o ConnectTimeout=5 %s /usr/bin/uname -n /usr/bin/ssh -o StrictHostKeyChecking=yes -o PasswordAuthentication=no -o ConnectTimeout=5 %s %s /usr/bin/scp -o StrictHostKeyChecking=yes -o PasswordAuthentication=no -o ConnectTimeout=5 %s %s:%s

Either don't enforce StrictHostKeyChecking or provide a means to override the command line.

Idea priority Medium
  • Guest
    Jan 29, 2024

    StrictHostKeyChecking is specified to ensure that the RDQM commands connect to, and execute on, the correct hosts. Establishing trust for the host keys should be a one-time operation that is performed when setting up the RDQM HA group and passwordless SSH for the mqm user. Please explain why establishing trust for the host keys is problematic for you. Thank you.