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 Delivered
Created by Guest
Created on Apr 21, 2020

Need configurable tuning parameter via qm.ini to suppress TCP/IP bad data FDCs

Our Enterprise MQ Queue Managers have a need to constantly be scanned by security scanning software and certificate managers that frequently create a large number of rrcE_BAD_DATA_RECEIVED FDCs, which in turn fills up the /var/mqm/errors file system.

The details in the FDC are always:
Component :- cciInvalidDataReceived
Program Name :- amqrmppa
Major Errorcode :- rrcE_BAD_DATA_RECEIVED
Probe Description :- AMQ9207: The data received from host '' on channel '????' is not valid.

We would like to have a qm.ini tuning parameter setting to have these FDCs suppressed.

We understand that there is an APAR to set an environment variable -

However there are cases such as systemd startup units where it is difficult to properly set a ENV variable on startup. Having it in the qm.ini as a tuning parameter is a better option to ensure it is picked up when the queue manager is started, no matter the method.

Idea priority Medium
RFE ID 141847
RFE Product IBM MQ
  • Guest
    May 18, 2022

    How does this implementation differentiate between intentional security scanning as the requester speaks about, and actual DOS or other probes?

  • Guest
    May 18, 2022

    I am going to guess that the security scans get more intense when MQ may be resetting the connection which gives the scanning software more reason to amp up probes. Then the scanning software does even more to try to break in on every kind of protocol.

  • Admin
    Mark Taylor
    May 18, 2022

    Raiser has verified that MQ 9.2.5 has suppressed these FDCs for the scenarios they were interested in.

    Default configuration was changed in 9.2.0 to remove need for control via environment variables.

  • Guest
    Jun 8, 2020

    We expect a future version of MQ to remove the need for any configuration (env var or ini file) to suppress these FDCs