Skip to Main Content

This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Feb 8, 2024

Maximum amount of items included in (scheduled) transfer as transfer property

The implementation of MFT agents is unstable, particularly in situations involving the transfer of hundreds of files. It frequently occurs that a transfer will stall, and the agents involved become unresponsive, requiring manual intervention. Repeated new releases and PMRs have not improved the stability of the product.

One addition to the transfer that would, at least in our case, improve stability, is to limit the number of items for a transfer if the source is a filesystem. This could be done by adding a property to the transfer definition. As an example, a standard transfer definition, with the attribute @maxMatches added to the <source>/<file> element:

<?xml version="1.0" encoding="UTF-8"?>

<request version="3.00" xmlns:xsi="" xsi:noNamespaceSchemaLocation="FileTransfer.xsd">






<sourceAgent QMgr="agent1qm" agent="AGENT1"/>

<destinationAgent QMgr="agent2qm" agent="AGENT2"/>


<item checksumMethod="MD5" mode="binary">

<source disposition="delete" recursive="false">

<file maxMatches="32">c:\sourcefiles\*.jpg</file>


<destination exist="error" type="directory">







Such a feature would allow a transfer to be split up in multiple smaller transfers, reducing the incidence of stalling transfers as well as the impact of a stalled transfer, and the need for manual intervention.

Idea priority High
  • Admin
    Mark Taylor
    Apr 23, 2024

    While we recognise some changes in this area would be desirable, they are not likely to be prioritised into any forseeable development plan over the next couple of years. Therefore this item is being declined.

  • Admin
    Mark Taylor
    Feb 20, 2024

    Merged several ideas into a single one, as they all stem from the same underlying requirement


Limit the number of items included in transfer when source is a filesystem

IBM MQ MFT is particularly unstable, especially when large numbers of files are being transferred. In my current environment, where a single transfer will often involve hundreds and sometimes thousands of files, transfers often stall, and agents w...
3 months ago in MQ, MQ Advanced & MQ Appliance 0 Not under consideration

Make transfers from filesystem to queue transactional

IBM MQ MFT is particularly unstable. Transfers involving more than a couple of dozen files will frequently stall, agents becoming unresponsive, requiring manual intervention. If, after such intervention, a given file to queue transfer is restarted...
3 months ago in MQ, MQ Advanced & MQ Appliance 0 Not under consideration

Allow users to limit the number of connections to a queue manager in the scope of a single file-to-queue transfer

The MFT agent process will attempt to PUT files in a transfer to their destination queue all at once. If the MAXHANDS property of a queue manager is smaller than the number of files in a single transfer, then the transfer will stall. The files tha...
3 months ago in MQ, MQ Advanced & MQ Appliance 0 Not under consideration