Failure of a file-to-message transfer
If a file-to- message transfer fails after the agent has started writing file data to the destination queue, the agent writes a message to the queue to indicate to an application consuming the messages that a failure has occurred.
The message written to the destination queue if a failure
occurs:
- Is blank
- Has the same IBM® MQ group ID as the previous message written to the destination queue by the agent
- Has the IBM MQ LAST_MSG_IN_GROUP flag set
- Contains additional IBM MQ message properties, if message properties are enabled. For more information, see the topic MQ message properties set by MFT on messages written to destination queues.
Example
A transfer is requested by running
the following command:
fteCreateTransfer -sa AGENT_JUPITER -da AGENT_SATURN -dq RECEIVING_QUEUE
-qmp true -qs 1K /tmp/source1.txt
The file source1.txt is 48 KB. The transfer splits
this file into 1 KB messages and writes these messages to the destination
queue RECEIVING_QUEUE. While the transfer is in progress, after the agent has written 16 messages to RECEIVING_QUEUE, a failure occurs at the source agent.
The agent writes a blank message to RECEIVING_QUEUE. In addition to the standard set of message
properties, the blank message has the following message properties
set:
usr.WMQFTEResultCode = 40
usr.WMQFTESupplement = BFGTR0036I: The transfer failed to complete successfully.
![[MQ 9.2.0.2 Mar 2021]](ng9202.gif)
From IBM MQ 9.2.0 Fix Pack 2 and
IBM MQ 9.2.2, when a
transfer from a file fails, because of a delimiter size check error, only one empty message is sent.
Additionally, the user properties are added to this message if transfer failure was due to the
delimiter exceeding the set size on the destination agent.