IBM Support

IT16874: BFGSS0067W unable to delete the source file due to the IOException: BFGIO0033E: there is an invalid checksum

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

  • File Transfer Edition (FTE) has a transfer that receives
    BFGSS0067W: The file has transferred successfully but the
     source agent was unable to delete the source file due to the
     following IOException:
     'BFGIO0033E: There is an invalid checksum for file
     <file name> and recovery is not possible'
    
    The explanation of the error is:
     BFGIO0033E
      There is an invalid checksum for file <insert_0> and recovery
      is not possible.
     Severity
     20 : Error
     Explanation
     A transfer of the file failed part way through. During the
     recovery operation the system discovered the contents of the
     file had been changed.
     Response
     Resubmit the transfer request again, if required.
    
    However, the file was not changing during the transfer.
    
    In a trace, the checksum values for both the source and
    destination are the same.
    
    The problem happens when an I/O user exit (IOExit) is used, for
    instance with FTEQDLSExit in use for IBM i QDLS files.
    

Local fix

  • Set maxInlineFileSize=0 in the agent.properties file
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of an IOExit, such as FTEQDLSExit, performing
    transfers with source disposition delete.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    In certain circumstances IBM MQ File Transfer Edition is unable
    to delete the source file whilst holding the lock on that file.
    One such scenario is when 'maxInlineFileSize' has been
    configured in the agent.properties file with a value of greater
    than zero. When unable to delete the file when holding the file
    lock, an attempt is made to delete the file without the lock in
    place. In this circumstance the agent checks that the checksum
    of the file to be deleted matches the checksum of what was
    transferred, this protects against deleting a file which has
    subsequently changed thus losing data.
    
    When the agent invoked an IOExit to calculate the checksum on a
    file it incorrectly appended a number of zero bytes to the
    checksum which were not present in the file. This resulted in a
    different checksum to the file actually transferred, and so the
    agent failed with BFGIO0033E as it believed the file had changed
    since transferred. The file had actually not changed but the
    method to calculate the checksum was in error.
    

Problem conclusion

  • The code which invokes an IOExit to calculate the checksum on a
    file has been modified to ensure that it calculates the checksum
    correctly, thereby preventing the BFGIO0033E. BFGIO0033E will
    still be seen where the file has actually changed as is the
    expected behaviour.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.0       7.0.4.7
    v7.5       7.5.0.8
    v8.0       8.0.0.6
    v9.0 CD    9.0.1
    v9.0 LTS   9.0.0.1
    
    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

    IT16874

  • Reported component name

    WMQ FILE TRANSF

  • Reported component ID

    5724R1000

  • Reported release

    704

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-09-01

  • Closed date

    2016-10-21

  • Last modified date

    2017-06-01

  • 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:
01 June 2017