IBM Support

IT34436: Zero byte content MQ messages gets generated during MFT File to Message transfers when using a prefix delimiter

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

  • A file transfer takes place for a "file to message" transfer,
    using a prefix delimiter to split the file content across
    multiple MQ messages.
    The file which is being transferred had a total of 150
    delimiters within it, so it was expected that 150 messages would
    be produced on the queue - but instead 151 messages were
    One of the generated messages on the queue had no message
    content, which was not expected.

Local fix

Problem summary

  • ****************************************************************
    Users using MFT to perform file-to-message transfers, using a
    file prefix delimiter to split the file content across multiple
    Platforms affected:
    During  file-to-message transfer with a prefix delimiter, empty
    messages were seen in the destination queue.
    These empty message were created due to the way the MFT
    transfer-chunk with prefix delimiter processing was performed on
    the destination agent.
    The destination agent processed the received data chunk by
    prioritising complete lines with an End-Of-Line (EOL) character
    first, and incomplete lines without an EOL character were
    processed when the rest of the data arrived to the destination
    If the incomplete line started with the prefix delimiter, then
    the destination agent created an empty content MQ message, which
    was then put to the destination queue for the file transfer.

Problem conclusion

  • MFT file-to-message processing with prefix delimiter has been
    updated such that empty messages will not be generated when
    write buffer is empty.
    The fix is targeted for delivery in the following PTFs:
    Version    Maintenance Level
    v9.1 LTS
    v9.2 LTS
    v9.x CD    9.2.1
    The latest available MQ maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'

Temporary fix


APAR Information

  • APAR number


  • Reported component name

    IBM MQ MFT V9.1

  • Reported component ID


  • Reported release


  • Status


  • PE




  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date


  • Closed date


  • Last modified date


  • 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 MFT V9.1

  • Fixed component ID


Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910"}]

Document Information

Modified date:
20 November 2020