APAR status
Closed as program error.
Error description
The destination file is deleted after successful transfer due to "BFGTR0077I: The destination agent was unable to determine the size of the file <file name> that it had written" exception when using a Protocol Bridge Agent to transfer a file to FTP server. If the source disposition for the managed transfer was set to "delete", then this also results in the source file being deleted.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: This issue affects users of: - The MQ v7.5.0 Managed File Transfer component. - The MQ v8.0.0 Managed File Transfer component. - The MQ v9.0.0 Managed File Transfer component. who are transferring a file to a file server using a Protocol Bridge agent as a destination agent. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: When a Protocol Bridge Agent was acting as the destination agent for a managed transfer, it performed the following processing when transferring a file to a FTP Server: 1. Connected to the FTP Server. 2. Created a temporary file (destination file name with ".part" extension) on the FTP Server. 3. Wrote the file data to the file system. 4. Renamed the file (removing the ".part" extension). 5. Disconnected from the FTP Server (this step unlocks the file). 6. If the file data has been written successfully, and no errors have been thrown from the FTP Server: - Connected to the FTP Server to query the final size and last modified date of the file that has just been written. - Disconnected from the FTP Server. 7. Else - Generated a "Failed" transfer progress message. - Published the progress message. In step 6, The transferred file could not be found to determine its size and last modified date therefore it reported file size as -2 and generated the following exception. "BFGTR0077I: The destination agent was unable to determine the size of the file '<filename>' that it had written." After it queried the file information, the agent performed checksum data verification (for example MD5) on the written file. However, during the checksum verification, it found the exception BFGTR0077 so it marked the transfer as failed, which caused a deletion of the file data that was written on the FTP Server. There are two possible reasons for the exception BFGTR0077 being generated: 1. The file was no longer available on the file server because it was moved to another location after transfer. 2. The listFormat attribute in the protocol bridge agent configuration was incorrect for the file server. The checksum data validation failed due to an incorrect list format therefore, the destination file was incorrectly deleted. However, the managed transfer still marked the transfer as successful because the file was written successfully and there was no error reported from the FTP server . If the source disposition for the managed transfer was set to "delete", then this would have also resulted in the source file being deleted.
Problem conclusion
The verification process of checksum data has been updated so that if the exception contains "BFGTR0077", it will keep the transfer of a file as successful and won't delete the file written on the destination. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v7.5 7.5.0.8 v8.0 8.0.0.7 v9.0 CD 9.0.3 v9.0 LTS 9.0.0.2 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
IT18616
Reported component name
WMQ MFT
Reported component ID
5724H7242
Reported release
750
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-12-30
Closed date
2017-03-27
Last modified date
2017-12-22
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 MFT
Fixed component ID
5724H7242
Applicable component levels
R750 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDEZSF","label":"IBM WebSphere MQ Managed File Transfer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
27 January 2022