IBM Support

PM82583: THE TRANSFERSET ELEMENT OF A WEBSPHERE MQ FILE TRANSFER EDITION AUDIT XML MESSAGE REPORTS BYTESSENT="0" AS AN ATTRIBUTE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The bytesSent attribute of the transferset element in a
    WebSphere MQ File Transfer Edition audit XML message has a value
    of "0" in all started, progress, and completed audit messages
    published by the agent. This is the case even when a
    successful transfer has occurred where all the data bytes have
    been received by the receiving WebSphere MQ File Transfer
    Edition agent.
    

Local fix

  • No local fix
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects all users of WebSphere MQ File Transfer
    Edition.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM SUMMARY:
    A WebSphere MQ File Transfer Edition source agent publishes
    XML audit messages to a subtopic of SYSTEM.FTE/Log regarding the
    state of a file transfer. During a normal, successful file
    transfer, the source agent first publishes a "started" XML audit
    message. That is then followed by a "progress" XML audit message
    once data has been sent and then finally, once the transfer
    has ended successfully, a "completed" XML audit message is
    published.
    
    However, when a transfer occurs from a z/OS source agent, both
    the "progress" and "completed" XML audit messages report
    bytesSent="0" in the transferset element of the TransferLog
    message that is published.
    
    This behaviour was due to the way in which the internal data
    structures of the WebSphere MQ File Transfer Edition agent are
    filled when reading from a dataset. This results in the source
    agent performing a checkpoint to occur earlier than would be
    expected on a distributed platform. As a result of this
    checkpoint, the "progress" and "completed" XML audit messages
    are generated on a different code path where some transfer
    information, such as the number of bytes sent, was not
    available. This therefore resulted in the bytesSent value
    being zero in the published XML audit message.
    
    The issue can occur on other platforms besides z/OS, however the
    size of the file data must exactly match the size of the
    internal data structure used to hold the "slices" of the data.
    Therefore the chances of hitting this issue on platforms other
    than z/OS are far smaller.
    

Problem conclusion

  • The WebSphere MQ File Transfer Edition agent has been updated so
    that no matter which code path taken to generate the progress
    and completed XML audit messages, transfer information such as
    the number of bytes sent are made available. This ensures the
    bytesSent value in the transferset element of the XML audit
    message can be set to the correct value in the published
    message.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Platform           v7.5
    --------           --------------------
    Multiplatforms     7.5.0.2
    
    Platform           v7.0
    --------           --------------------
    Multiplatforms     7.0.4.3
    
    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

    PM82583

  • Reported component name

    WMQ FTE Z/OS

  • Reported component ID

    5655U8000

  • Reported release

    704

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-02-12

  • Closed date

    2013-03-25

  • Last modified date

    2013-03-25

  • 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 FTE Z/OS

  • Fixed component ID

    5655U8000

Applicable component levels

  • R704 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCPQ63","label":"APAR \/ Maintenance"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"704","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"704","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
25 March 2013