Skip to Main Content
IBM Sterling


This portal is to open public enhancement requests for IBM Sterling products and services. 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.

1 Not supported for the current status
Status Under review
Categories APIs & SDKs
Created by Guest
Created on Jun 23, 2026
Merged idea
This idea has been merged into another idea. To comment or vote on this idea, please visit ITX-I-422 Enhance ITX MMap Execution Control with Native Timeout, Safe Termination and External Process Lifecycle Management.

Enhance ITX MMap Execution Control with Native Timeout, Safe Termination, and External Process Lifecycle Management Merged

We are using IBM Transformation Extender (ITX) 11.0.2 TX Programming Interface (MMap / mpiMapRun) in a high-throughput, containerized production environment (AKS).
We have implemented the recommended lifecycle:- load → run → abort (if needed) → wait → unload
However, based on production behavior and confirmed by IBM support:
1. abortRun() is cooperative and does not guarantee termination2. unload() cannot be safely invoked while execution is active3. There is no API-level timeout or enforced execution limit4. External processes (e.g. OpenPGP/GPG) are not monitored and may remain as zombie processes5. In certain scenarios, map.run() does not return and may consume CPU indefinitely
This results in:- CPU saturation (100% sustained)- Thread pool exhaustion- Persistent request rejection (HTTP 429)- System unable to recover without process/container restart
In modern cloud environments, this behavior is not manageable because:- Execution cannot be preempted or bounded deterministically- A single stuck execution can exhaust the system- Restart-based recovery leads to instability under load
These limitations prevent safe scaling and operation in production for high-throughput workloads.

What is your industry? Travel & Transportation
How will this idea be used?

This enhancement will be used to enable safe, reliable, and scalable execution of ITX maps in a cloud-native environment.
Specifically, it will allow us to:
- Enforce execution time limits on map.run()- Prevent CPU runaway caused by non-terminating executions- Safely terminate stuck or long-running maps- Avoid reliance on container restarts as a recovery mechanism- Improve system stability under high concurrency and burst traffic
In our use case (logistics and supply chain processing under DHL), we process large numbers of integration requests in parallel. Without deterministic execution control:
- A small number of stuck executions can exhaust all compute resources- System throughput drops to zero despite incoming traffic- SLA compliance is impacted due to inability to process requests
These enhancements will allow ITX to operate reliably in high-throughput, distributed environments such as AKS and other container platforms.
This is critical for enterprise workloads where predictable execution behavior, resource control, and fault isolation are required.