IBM Support

IT41242: MFT Audit Information can incorrectly report DESTINATION_FILE_SIZE as -1 for a recovered transfer request

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

  • Upon failover of a high availability IBM MQ MFT agent, the
    Logger will record DESTINATION_FILE_SIZE=-1 for the  recovered
    managed transfer.  This is even though the transfer is
    successful and has the same SOURCE_CHECKSUM_VALUE and
    DESTINATION_CHECKSUM_VALUE.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of MQ Managed File Transfer.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When an MQ Managed File Transfer agent is acting as the
    destination agent for a transfer request containing multiple
    files and the agent is stopped immediately and restarted,
    entered agent recovery or fails over to the standby agent.  It
    is possible that the destination agent completed the one of the
    file items, but did not send the audit information to the
    sending agent.  So that when destination agent recovers the
    transfer request, the audit information can have
    DESTINATION_FILE_SIZE set to -1 and an empty
    DESTINATION_LAST_MODIFIED value.  This results in the transfer
    summary information showing the destination size as -1 and last
    modified value being empty.
    

Problem conclusion

  • The code has been changed to make a further attempt to obtain
    the destination size/last modified attribute if available after
    the agent has started.  There are still valid reason why the
    DESTINATION_FILE_SIZE could be -1.  One example would be if the
    destination file has been move by another process.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.2 LTS   9.2.0.7
    v9.3 LTS   9.3.0.2
    v9.x CD    9.3.1
    
    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

    IT41242

  • 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-06-15

  • Closed date

    2022-09-08

  • Last modified date

    2022-09-30

  • 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:
30 September 2022