Skip to Main Content
Integration


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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - 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
Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit MESNS-I-666 Maximum amount of items included in (scheduled) transfer as transfer property.

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

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 will become unresponsive, requiring manual intervention.

When the source for a scheduled transfer is a filesystem, the transfer will automatically include all the files that match the pattern, with no moderation possible. If the transfer is not concluded within the scheduled interval for this (repeating) transfer, MFT will start a new transfer, which includes the same (large) batch of files, which will also stall. If we are, through manual intervention, somehow able to restart the transfer, the files in it are delivered *again*, because the transfer is not a transactional process.

A simple addition to the transfer definition will allow us to limit the number of items if the source is a file system. This would reduce the number of stalled transfers, unresponsive agents, and need for manual intervention. As an example, I'll include a sample transfer definition with an added @maxMatches attribute in the <source/file> element:

<?xml version="1.0" encoding="UTF-8"?>
<request version="3.00" xmlns:xsi="https://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="FileTransfer.xsd">
  <managedTransfer>
    <originator>
      <hostName>example.com.</hostName>
      <userID>fteuser</userID>
    </originator>
    <sourceAgent QMgr="agent1qm" agent="AGENT1"/>
    <destinationAgent QMgr="agent2qm" agent="AGENT2"/>
    <transferSet>
      <item checksumMethod="MD5" mode="binary">
        <source disposition="delete" recursive="false">
          <file maxMatches="32">c:\sourcefiles\*.jpg</file>
        </source>
        <destination exist="error" type="directory">
          <file>/targetfiles/images</file>
        </destination>
      </item>
    </transferSet>
  </managedTransfer>
</request>
Idea priority High