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.


Add a new idea Subscribe
Status Not under consideration
Workspace MQ, MQ Advanced & MQ Appliance
Created by Guest
Created on Feb 8, 2024

RELATED IDEAS

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.

Make transfers from filesystem to queue transactional Merged

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, all the files that were submitted to the queue during an earlier attempt will be put to the queue again, and processed by the receiving applications a second time. In my environment, this frequently occurs. In my situation it is not usually harmful, since the receiving application is robust enough - but I can imagine this is not always the case.

Might it be possible to make it so that file to queue transfers are first committed to temporary system queues, and only committed to the specified target queue after the entire transfer has been successfully completed?

Idea priority Medium

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.