Fixes are available
APAR status
Closed as program error.
Error description
When performing a message-to-file transfer, if an invalid filename name is specified then the transfer fails, as expected, with an appropriate error message logged to the WebSphere MQ FTE Transfer Log, such as: . BFGRP0034I: The file transfer request has completed with no files being transferred. BFGIO0045E: The specified data set name is not a valid data set name. . However, after the transfer processing completes, the input messages are not rolled back to the source queue specified in the transfer request. As such, the message data is lost as it no longer exists on the source queue or destination file.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: This issue affects users of WebSphere MQ File Transfer Edition performing a message to file transfer, where the transfer request message specifies one queue (with one or more messages) to be transferred to one destination file. Platforms affected: MultiPlatform **************************************************************** PROBLEM SUMMARY: When performing a message to file transfer, where the transfer request message specifies a single transfer item from an input queue (containing one or more messages) to a single destination file, messages are read off the input queue under a WebSphere MQ sync-point. This allows the sync-point to be backed out to return to source messages to the input queue in the case where the requested transfer fails. If an invalid filename (or dataset name for z/OS destinations) was specified as part of the transfer request, the transfer would fail and the sync-point under which the source messages read is backed out. However this scenario also caused the WebSphere MQ FTE source agent to perform recovery processing that resulted in the source messages being destructively read from the input queue (not under a sync-point) a second time. As the requested transfer had previously ended (as a failed transfer) the agent did not put the messages back on the input queue causing the message data to be discarded.
Problem conclusion
The WebSphere MQ FTE agent code has been modified to ensure that the agent does not perform recovery processing after a message-to-file transfer fails when an invalid destination name is specified as part of a transfer request that includes a single transfer item (i.e., a single input queue, with one or more messages, to a single destination file). This ensures the source messages are rolled back to the input queue when the sync-point is backed out. Additionally, in the case of recovery processing, messages are now always re-read under sync-point and this sync-point is committed only if the destination agent is known to have successfully completed the transfer at the destination end. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v7.0 7.0.4.4 v7.5 7.5.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
PM90662
Reported component name
WMQ FTE Z/OS
Reported component ID
5655U8000
Reported release
704
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-06-07
Closed date
2013-09-26
Last modified date
2018-07-31
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 FTE Z/OS
Fixed component ID
5655U8000
Applicable component levels
R704 PSY
UP
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"WebSphere MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"704"}]
Document Information
Modified date:
01 November 2021