Joined: 25 Mar 2003 Posts: 2538 Location: Melbourne, Australia
varunraot wrote:
Few comments from my end
...I am talking about "embedded agent" from IIB ( and not the standalone MQ MFT agent) which is not really robust when it comes to the transfer of high volume of data.
I had engaged IBM Product team for over 6 months in analyzing the behavior, pattern and root cause. This is what they concluded
"We expect that in flight transfers already in the queue will eventually complete. For transfers that experience this error (BFGSS0030W : The agent is already acting as the source agent for the maximum number of file transfer operations and unable to queue further requests,
due to the queued transfer limit of XXXX being reached. The new transfer request will not be carried out) they will need to be resubmitted (so the message flow needs to be re-run)."
This could be purely a capacity and configuration issue. Increase the limits so that the transfers can run. If they are small files, MFT should be able to complete them at least 30 per second, subject to external constraints (CPU, I/O, network, etc).
Consider combining the files into one larger file. Use compression. MFT easily handles multi-GB files.
This will reduce the overhead in MFT / MQ. The combined data could include all the sequencing requirements!
Another possibility is for the IIB flow to generate file transfer request XML messages and put them directly to the command queue of a MFT agent that is outside of IIB. We use this technique. _________________ Glenn
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum