Skip to Main Content
IBM Data and AI Ideas Portal for Customers

This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

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.

IBM Employees should enter Ideas at

Status Not under consideration
Created by Guest
Created on Dec 1, 2020

FTM SWS, Enhanced resilience in z/OS High Availability configuration.


Having FTM SWS running in High Availability mode across several z/OS lpars.


If one FTM SWS on one lpar encounters a problem it should "step back" and let other remaining FTM SWS on other lpars take care of the workload, instead of keep competing with them to get a share of the work, and then fail to complete the work.

The FTM SWS that is having some sort of trouble with completing work successfully, should not continue taking in work, fail, take in more work, fail again, and so on.

Instead it should enter a "problem mode of operation" and then idle itself temporarely.

When entering "problem mode of operaton" : issue a message for alerting (and/or automation if relevant).

While in "problem mode of operaton" : Try probing at regular intervals if the situation still exists.

If the probing indicate the problem no longer exists : then exit the "problem mode of operaton" , spin up and start competing for work.

When exiting "problem mode of operaton" : issue a message for de-alerting (and/or automation if relevant).

Such a mechanism could be relevant for FTM user nodes as well for internal FTM code/modules/nodes/etc.


We have FTM SWS in HA mode across 4 z/OS lpars.

In one case DB2 resources were depleted on one lpar, with the result that FTM SWS on this lpar could not complete the work it had taken on.

In this case FIN messages could not be processed by the DnfErQueueInput node.

The msg was read from MQ, processing failed due to DB2 issues, and the msg was put back on the queue,

and was either

- read again by the this FTM SWS and was either a) processed successfully this time, or b) put back once more.

- read by another FTM SWS on another lpar and processed successfully there.

Some msgs were failed twice by the same FTM SWS and were returned to the application by use of the reply-to-queue.

The above is as described for the DnfErQueueInput FTM user node.

The idea is that the node that experience problems, stops taking on more work, and let other FTM SWS on other lpars take care of the workload.

At the same time we saw the MSIF fileact DNF_O_FT CIN issued DNFO9010E announcing that it stopped processing messages.

As above, we suggest that the MSIF fileact is only stopped/paused on the lpar with the issue and not globally.