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.
|Component||High Availability, Zero Downtime|
|Priority||Medium - Important|
|IBM's success depends on gathering feedback from customers like yourself. Aha Ideas Portal is the third party tool through which IBM Offering Managers gather feedback from customers such as yourself.|
|IBM is a global organization with business processes, management structures, technical systems and service provider networks that cross borders. As such, the information collected through Aha Ideas Portal (Customer Name, Customer Email Address) will be stored by them in the United States, and handled only as per IBM's instructions and policies. Your data (Name and Email Address) will NOT be shared with other IBM customers.|
|In order to safeguard your information in Aha, do not leave your workstation unattended while using this application, log off after using it, and print only if necessary. If you need to make a hardcopy, remember to pick up the print-out immediately, keep it under lock, and destroy it immediately when no longer needed.|
|NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "firstname.lastname@example.org" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions|