IBM Support

IT42339: Bad data arrived at MQ's socket in an MQ client application, butthe required FDC was not written

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

  • Bad data was received at MQ's socket.  In this case MQ has to
    write an FDC record under /var/mqm/errors, to enable
    investigation of the bad data.
    
    Instead, no FDC was written, but an error message was written,
    including this text:
    
    AMQ9213E : The return code from the TCP/IP (ioctl) call was 9.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Client applications (or server-side MQ code) in which some bad
    data is received at MQ's socket.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    After receiving data it cannot understand, the MQ library code
    running in the application intends to write an FDC file.
    
    First, this MQ code attempts to read any further data there
    might be in the TCP/IP receive buffer, so it may be included in
    the FDC dumps.  To find whether there is any data, MQ first
    calls ioctl.
    
    If this ioctl call fails for any reason, the MQ code does not
    then write the FDC file.  But it should have continued to write
    the FDC file with the data it had successfully received before
    the ioctl call.
    

Problem conclusion

  • The MQ code has been corrected so that it will continue to write
    the FDC file with the data it had successfully received before
    the ioctl call, even if the ioctl call fails.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.2 LTS   9.2.0.10
    v9.3 LTS   9.3.0.5
    v9.x CD    9.3.2
    
    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

    IT42339

  • Reported component name

    MQ BASE V9.2

  • Reported component ID

    5724H7281

  • Reported release

    920

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-10-26

  • Closed date

    2022-12-22

  • Last modified date

    2022-12-22

  • 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

    MQ BASE V9.2

  • Fixed component ID

    5724H7281

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"920","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 December 2022