IBM Support

IT03450: NEW FUNCTION TO REQUEST A TRANSFER BE REPORTED AS FAILED IF ANY FILES FAIL TO TRANSFER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • This APAR adds new functionality to WebSphere MQ Managed File
    Transfer which allows agents to be configured to fail a managed
    transfer, as soon as a transfer item within that managed
    transfer fails.
    
    When the functionality has been enabled, agents will start
    processing managed transfer requests as normal. However, as soon
    as a transfer item fails, then the managed transfer is marked as
    failed and no further transfer items will be processed. For the
    transfer items that were successfully processed before the
    managed transfer failed:
    
    - The source disposition for those transfer items will be
    honoured (for example, if the source disposition for the
    transfer item was set to "delete", then the source file will be
    deleted).
    - The destination files that were written will remain on the
    destination file system and will not be deleted.
    
    To enable this new function, the user must set the following new
    property in the source agent's agent.properties file:
    
      failTransferOnFirstFailure
    
    to the value "true". For example:
    
      failTransferOnFirstFailure=true
    
    The default value is "false".
    
    In addition to the source agent having the
    "failTransferOnFirstFailure" agent property set to the value
    "true", the destination agent for the managed transfer must also
    have this APAR applied for the new function to be active.
    
    Example
    ----------
    Consider a managed transfer request which consists of 5 transfer
    items:
    
    - file1.txt
    - file2.txt
    - file3.txt
    - file4.txt
    - file5.txt
    
    The source disposition for each of these transfer items is set
    to "delete".
    
    When the "failTransferOnFirstFailure" has not been set to the
    value "true" on the source agent for the managed transfer, if
    transfer item 3, fails to transfer (perhaps because the file
    file3.txt does not exist) then managed transfer continues and
    attempts to process transfer items 4 and 5 (ie. file4.txt and
    file5.txt). The managed transfer is then marked as being
    "Partially Successful" in the final transfer log publication for
    the managed transfer, and the source files file1.txt and
    file2.txt are deleted.
    
    When this new functionality has been enabled, if file3.txt fails
    to transfer, then the managed transfer fails and the source
    agent does not attempt to process transfer items 4 and 5 (ie.
    the source agent does not try to move file4.txt and file5.txt).
    The managed transfer is marked as "Failed" in the final transfer
    log publication for the managed transfer. The first two source
    files, file1.txt and file2.txt, that were successfully
    transferred, are deleted by the source agent. The corresponding
    files (file1.txt and file2.txt) remain on the destination file
    system and are not deleted.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This new function will be active when:
    
      1) a WebSphere MQ Managed File Transfer source agent has this
    APAR applied,
    
      2) the following property is set in this source agent's
    agent.properties file:
    
          failTransferOnFirstFailure=true
    
      3) the destination agent for this transfer also has this APAR
    applied.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    Without this new function, if a managed file transfer contained
    multiple files and one of these files failed to transfer (for
    example because the destination file already existed and the
    overwrite property is set to "error"), the source agent would
    continue and attempt to transfer any remaining files in the
    request. The transfer log data for this managed transfer would
    then display this transfer as having a "Partially Successful"
    result.
    

Problem conclusion

  • This new function ensures that, after one file in the managed
    transfer request fails to be transferred, the managed file
    transfer is aborted and none of the remaining files are written
    to the destination file system. The transfer log for the managed
    transfer then displays this transfer as having a "Failed"
    result. Any post destination or post source commands specified
    as part of the managed transfer request are not executed.
    
    Any files specified in the managed file transfer that were
    successfully transferred, before a subsequent file fails to be
    transferred, remain on the destination file system and are not
    deleted.
    
    Aborted files in the managed transfer request are highlighted in
    the "progress" transfer log message with the following message:
    
      "BFGTR0076E: This file has not been transfered due to a
    previous file in this transfer failing."
    
    
    Below is a snippet from an example transfer log "progress"
    message showing this behaviour:
    
    
    
            /home/user1/files_out/file2.txt
            ff1e0283123d14cf8bd52ac449770017
    
    
            /home/user1/files_in/file2.txt
            ff1e0283123d14cf8bd52ac449770017
    
    
    
    
    
            /home/user1/files_out/file3.txt
    
    
            /home/user1/files_in/file3.txt
    
    
            BFGIO0001E: File "/home/user1/files_out/file3.txt" does
    not exist.
    
    
    
    
            /home/user1/files_out/file4.txt
    
    
            /home/user1/files_in/file4.txt
    
    
            BFGTR0076E: This file has not been transfered due to a
    previous file in this transfer failing.
    
    
    
    
    The final transfer log publication for the managed transfer
    contains the following transfer status information:
    
    
        BFGRP0037I: The file transfer request has been failed due to
    a failure to transfer a file.
    
    
    
    Note, if the source disposition was set to "delete" for any of
    files that were successfully transferred in the managed transfer
    request, the source agent will continue to try and delete these
    source files at the end of the transfer. For the example, in the
    example snippet (above) of a Transfer Log "progress" message,
    file2.txt was successfully transferred so the source agent will
    attempt to delete this file.
    
    In addition, the file transfer will be marked as "Failed" in the
    case where all of the files are successfully transferred but one
    (or more) of the source files could not be deleted when the
    source disposition was set to "delete".
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.5       7.5.0.6
    v8.0       8.0.0.4
    
    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

    IT03450

  • Reported component name

    WMQ FTE

  • Reported component ID

    5724H7242

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-07-29

  • Closed date

    2015-09-24

  • Last modified date

    2015-09-24

  • 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

  • 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:
24 September 2015