IBM Support

IT02238: WMQ FTE DETAILED REPLY MESSAGES DO NOT CONTAIN INDIVIDUAL TRANSFER ITEM RESULTS.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When the "detailed" attribute on the  element within a
    managed transfer request XML message is set to the value
    "true", the source agent for the transfer should generate reply
    messages containing information on the transfer success (or
    failure) of each item in the managed transfer request.
    
    However, when using WebSphere MQ FTE v7.0.4.4 (which introduced
    this new "detailed" attribute) the information regarding each
    transfer item was omitted from the reply messages. Only the
    meta-data and  element attributes would be included.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of WebSphere MQ File Transfer Edition
    v7.0.4.4 who use the detailed reply message functionality on
    managed call and managed transfer requests that are submitted to
    an agent.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When using WebSphere MQ File Transfer Edition (FTE) v7.0.4.4,
    more information can be included in the reply messages sent by a
    source agent processing the request.
    
    Reply messages can be requested when the "reply" element is
    specified within a managed call or managed transfer XML request
    messages that are put to an agent's SYSTEM.FTE.COMMAND queue. An
    example of such an XML is as follows:
    
    ?xml version="1.0" encoding="UTF-8"?>
    
    
    
                127.0.0.1
                mqm
    
    
    
            FTE_REPLY_MSGS_QUEUE
    
    
    
                        C:\files\out\myfile.txt
    
    
                        C:\files\in\myfile.txt
    
    
    
    
    
    
    
    A new "detailed" attribute on the  XML element can be specified
    from WebSphere MQ FTE v7.0.4.4 which accepts either the value
    "true" or "false".
    
    When the "detailed" attribute on the  XML element was set to the
    value "true", for example:
    
      FTE_REPLY_MSGS_QUEUE
    
    the source agent should have included all of the information
    contained within the  element of the transfer log "progress" XML
    messages (that are published to the SYSTEM.FTE/Transfers/ topic)
    in any reply messages put to the specified queue on the
    specified queue manager. However, only an empty  element with
    associated attributes was being included, except for the final
    detailed reply message which also nested any meta-data
    information for a particular managed call / transfer request. No
    details on the individual transfer items was included as would
    have been expected.
    

Problem conclusion

  • The WebSphere MQ File Transfer Edition agent code has been
    updated such that when detailed reply messages are requested,
    all of the  data published to the SYSTEM.FTE/Transfers/ topic in
    transfer log "progress" messages, is also included in the reply
    messages returned by the source agent.
    
    Note that the number of reply messages produced per managed call
    or managed transfer request is equal to:
    
      1 + [the number of transfer log progress messages published to
    the SYSTEM.FTE/Transfers/ topic]
    
    Only the final reply message contains meta-data information and
    the overall result code for the managed call or managed transfer
    request.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.0       7.0.4.5
    
    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

    IT02238

  • Reported component name

    WMQ FILE TRANSF

  • Reported component ID

    5724R1000

  • Reported release

    704

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-06-05

  • Closed date

    2014-07-31

  • Last modified date

    2014-08-15

  • 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 FILE TRANSF

  • Fixed component ID

    5724R1000

Applicable component levels

  • R704 PSY

       UP

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

Document Information

Modified date:
15 August 2014