APAR status
Closed as program error.
Error description
When using a resource monitor which creates a transfer which deletes the source file when complete, the file is triggered on twice resulting in two transfers for the same file. The first transfer completes successfully, and the second transfer causes the error below as the source file no longer exists: BFGIO0001E: File "file name" does not exist. The resource monitor should not have triggered on the file more than once.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: This issue affects all users of IBM MQ Managed File Transfer who are using directory resource monitors to trigger transfers on matched files with a source disposition value of "delete". Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: When an IBM MQ Managed File Transfer directory resource monitor triggered on a file, a request to transfer that file was submitted to the agent that would delete the source file should it be successfully transferred. A race condition existed which could cause a second trigger on that same file if it was deleted whilst the directory resource monitor was scanning for matching files on a subsequent poll. The race condition would occur if the directory resource monitor obtained a list of files from the monitored directory but one of those files was subsequently deleted before the directory resource monitor could check whether the file was eligible for triggering. If this situation occurred, the directory resource monitor would trigger on the deleted file and a second transfer attempt would be made. This would subsequently fail as the source file was no longer present on the filesystem and result in the second transfer for the same file failing with the BFGIO0001E error message. The original transfer would complete successfully.
Problem conclusion
The IBM MQ Managed File Transfer directory resource monitor code has been updated to remove the race condition (noted in the Problem Summary section) and thus prevented a second triggering of the resource monitor on a file that is deleted whilst the resource monitor is polling the directory. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v8.0 8.0.0.6 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
IT13688
Reported component name
WMQ MFT V8.0
Reported component ID
5724H7252
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-02-09
Closed date
2016-04-25
Last modified date
2016-04-25
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 V8.0
Fixed component ID
5724H7252
Applicable component levels
R800 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
25 April 2016