IBM Support

IT18213: MQ MFT Message-to-File transfer creates zero-byte destination file

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using IBM MQ Managed File Transfer V7.5.0.6 (MFT) to
    perform a message-to-file transfer, the transfer request
    completes successfully but the destination file that is written
    for the transfer contains no data (i.e., is 0 bytes in size) and
    the source message for the transfer is not removed from the
    queue.
    
    This occurs when the transfer request XML message is constructed
    by a user written application where the value of the groupId
    attribute of the <queue> element, for example:
    
      414D5120514D76383020202020202020AEE9F55823846E02
    
    in the following XML snippet:
    
    <queue
    groupId="414D5120514D76383020202020202020AEE9F55823846E02"
    useGroups="true">SOURCEQ7506</queue>
    
    matches both the message identifier of the source message to
    transfer for the request and the message identifier of the
    transfer request command message that is put to the source
    agent's SYSTEM.FTE.COMMAND queue.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of:
    
    - WebSphere MQ File Transfer Edition V7.0.4.6
    - The WebSphere MQ V7.5.0.6 and later Managed File Transfer
    component
    - The IBM MQ V8.0.0.5 and later Managed File Transfer component
    - The IBM MQ V9 Managed File Transfer component
    
    that have the fix for APAR IT12173.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When an IBM MQ Managed File Transfer V7.5.0.6 (MFT) agent
    performed a message-to-file (M2F) transfer and the value of the
    groupId attribute matched the transfer identifier, the agent
    attempted to match on the MQMD message identifier field when
    consuming the message from the source queue.
    
    This occurred when the transfer request XML message was
    constructed by a user written application where the value of the
    groupId attribute of the <queue> element, for example:
    
      414D5120514D76383020202020202020AEE9F55823846E02
    
    in the following XML snippet:
    
    <queue
    groupId="414D5120514D76383020202020202020AEE9F55823846E02"
    useGroups="true">SOURCEQ7506</queue>
    
    matched both the message identifier of the source message to
    transfer for the request and the message identifier of the
    transfer request command message that was put to the source
    agent's SYSTEM.FTE.COMMAND queue.
    
    Note the transfer identifier of a transfer is determined by
    using the message identifier of the transfer request XML message
    submitted to the agent's SYSTEM.FTE.COMMAND.
    
    Because the agent tried to match on the groupId attribute rather
    than the messageId it received an MQRC 2033
    MQRC_NO_MSG_AVAILABLE and resulted in an empty file (0 byte)
    being written to the destination as well as left the source
    message on the queue.
    

Problem conclusion

  • The Managed File Transfer product code has been updated to
    restore the comparison check of the transfer identifier and the
    value of the groupId attribute within the transfer request XML
    payload.  If these two identifiers are equivalent, the source
    agent will use the identifier as a message identifier match
    option (as opposed to a group identifier match option) for the
    first MQGET attempt that is made on the input queue for the
    message-to-file transfer.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.0       7.0.4.7
    v7.5       7.5.0.9
    v8.0       8.0.0.8
    v9.0 CD    9.0.4
    v9.0 LTS   9.0.0.2
    
    The latest available FTE maintenance can be obtained from
    'Fix List for WebSphere MQ File Transfer Edition 7.0'
    http://www-01.ibm.com/support/docview.wss?uid=swg27015313
    
    The latest available MQ 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

    IT18213

  • Reported component name

    WMQ MFT

  • Reported component ID

    5724H7242

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-12-02

  • Closed date

    2017-05-26

  • Last modified date

    2018-08-02

  • 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

    WMQ MFT

  • Fixed component ID

    5724H7242

Applicable component levels

  • R750 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSCUHLE","label":"WMQ Managed File Transfer"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 August 2018