IBM Support

IT30348: Allow suppression of TCP/IP bad data FDCs

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Attempting to connect a non-MQ client to an IBM MQ TCP/IP
    listener will cause the queue manager to write an AMQ9207 error
    message to the queue manager error logs, if the initial data
    transmission is not recognised by IBM MQ. A failure data capture
    (FDC) record is also written. This APAR adds the ability via
    environment variable "AMQ_NO_BAD_COMMS_DATA_FDCS" to suppress
    the generation of these diagnostic files when the initial
    communications data flow is not recognised by IBM MQ.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users who use port scanners or send non-MQ protocol traffic to
    an MQ listener port to check the listener is accepting
    connections may potentially wish to prevent this type of
    activity from generating FDC records.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    Attempting to connect a non-MQ client to an IBM MQ TCP/IP
    listener caused a queue manager to write an AMQ9207 error
    message to the queue manager error logs, as the protocol data
    was not recognised by IBM MQ, an FDC record is also written. The
    FDC files needed to be inspected and archived/deleted to free
    disk space.
    

Problem conclusion

  • An environment variable "AMQ_NO_BAD_COMMS_DATA_FDCS" is
    provided, when set, this instructs IBM MQ to not generate FFSTs
    when reporting AMQ9207 errors on the initial communications
    flow. To be effective, the environment variable should be set
    when the queue manager and listener processes are started.
    
    The FDC will continue to be generated in the case where a client
    sends valid MQ protocol flows to the queue manager, and then
    sends invalid data, as this is indicative of a client issue that
    warrants further investigation.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.14
    v9.0 LTS   9.0.0.9
    v9.1 CD    9.1.5
    v9.1 LTS   9.1.0.5
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT30348

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7251

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-09-23

  • Closed date

    2019-10-31

  • Last modified date

    2019-10-31

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    IBM MQ BASE MP

  • Fixed component ID

    5724H7251

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.0.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
31 October 2019