APAR status
Closed as program error.
Error description
In the MQ V8 Managed File Transfer component, the source disposition for a managed transfer is being processed when the source agent receives the final "Progress" message for that transfer from the destination agent, rather than when the transfer has completed. This causes issues if an agent has been configured to run a SourceTransferEndExit or DestinationTransferEndExit which tries to access the source file. These exits are run after the final "Progress" message has been processed, which means that if the source disposition for the managed transfer is set to "delete", then the source file will be deleted before the exits run.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: This issue affects users of the IBM MQ V8 and V9 Managed File Transfer component who have: - Agents which process managed file transfers that have the -sd (source disposition) parameter set to the value "delete". - SourceTransferEndExits and/or DestinationTransferEndExits configured on those agents which perform some processing on the source file for a managed transfer. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: During the processing of a managed transfer, a number of internal messages are sent between the Source and Destination Agents indicating how the managed transfer is progressing. The messages include a "Progress" message (showing the number of transfer items that have been processed, and the number of bytes that a Destination Agent has written), and a "Completed" message (when the Destination Agent has finished handling all of the transfer items in the managed transfer). After the Destination Agent has sent the last "Progress" message for a managed transfer, it will run any DestinationTransferEndExits that have been configured. Once the exits have run and completed their processing, the Destination Agent will send the internal "Completed" message to the Source Agent. When the Source Agent receives this "Completed" message, it will run any SourceTransferEndExitsthat have been configured. After the exits have finished, the Source Agent marks the managed transfer as "Completed". When using : - the WebSphere MQ V7.0.4 File Transfer Edition product - the WebSphere MQ V7.5 Managed File Transfer component if a transfer item for a managed transfer has the -sd (source disposition) parameter set to the value "delete", then the Source Agent would delete the source file when it received an internal "Completed" message for that managed transfer. In the MQ V8.0 and V9.0 Managed File Transfer components, this behaviour changed, so that the Source Agent would delete the source file for the transfer item when it received an internal "Progress" message indicating that the Destination Agent had finished processing that transfer item. This meant that the source file for a transfer item would be deleted before any SourceTransferEndExits or DestinationTransferEndExits had been invoked. If those exits tried to access the source file as part of their processing, then they would encounter an error and the source file no longer existed.
Problem conclusion
The MQ V8.0 and V9.0 Managed File Transfer component has been updated so that the -sd (source disposition) parameter for a transfer item is only processed by the Source Agent when it receives a "Completed" message for the managed transfer containing that item from the Destination Agent. This ensures that the source file remains on the system when any: - SourceTransferEndExits that have been configured on the Source Agent - DestinationTransferEndExits that have been configured on the Destination Agents are run. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level 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
IT15361
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-05-19
Closed date
2016-07-26
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 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:
01 June 2017