IBM Support

IC98825: WMQFTE 7.0.4.1 TRANSFER WITH DELETE OF SOURCE, DOES NOT DELETE FILE IF SIZE OF FILE OVER 1.5 GB.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • WMQFTE 7.0.4.1 SFTP Bridge Agent has scheduled transfer that
    is set to delete the source file after the transfer is
    complete. If the source file is over 1.5 GB the delete of file
    is not completed. The file transfer does complete.
    The following error can occur
    BFGSS0067W: The file has transferred successfully but the
    source agent was unable to delete the source file due to the
    following IOException: 'inputstream is closed'
    .
    This error can be caused by a slow network connection. As the
    source agent must reread the file to verity file has not
    changed during the transfer.
    

Local fix

  • Manually delete the file after transfer.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users WebSphere MQ File Transfer Edition
    V7.0.4 and and WebSphere MQ Managed File Transfer V7.5 who are
    using the protocol bridge agent functionality to transfer a file
    from an SFTP server.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM SUMMARY:
    The issue occurred when a user attempted to transfer a file from
    an SFTP server (source) using a protocol bridge agent to a
    location using an agent with the option to delete the source
    file. The file took some time to delete and on some occasions
    was not deleted at all with the following error being returned:
    
    BFGSS0067W: The file has transferred successfully but the source
    agent was unable to delete the source file due to the
    following IOException: 'inputstream is closed'
    
    The issue arose because the verification of the source file,
    before the delete, introduced a notable period of delay or the
    connection timed out. The reason for this was because the source
    file was re-read from the source for an MD5 checksum to verify
    the file had not changed. Even when the transfer was specified
    with checksum="none", the file was still re-read.
    

Problem conclusion

  • When creating a transfer, the checksum -cs paramater on
    ftecreatetransfer can be set to "MD5" or "none" to indicate
    the validation method to use. The fix for this APAR is to
    carry out a basic validation on the file without re-reading
    the source file again when "none" has been specified.
    
    To execute the basic validation before deleting the source file,
    set the checksum to "none" on the transfer using the -cs
    parameter on ftecreatetransfer. More information about the -cs
    (checksum) parameter can be found on the following infocenter
    page for ftecreatetransfer:
    
    http://pic.dhe.ibm.com/infocenter/wmqfte/v7r0/topic/com.ibm.wmqf
    te.doc/start_new_transfer_cmd.htm
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.0       7.0.4.5
    v7.5       7.5.0.4
    v8.0       8.0.0.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

    IC98825

  • 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-01-20

  • Closed date

    2014-02-28

  • Last modified date

    2015-07-11

  • 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:
11 July 2015