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 (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 updateson 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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
CBT automatic reconnect according to SWIFT "best practice"
We faced in production an abort of our FIN LTs with SWIFTs abort reason codes saying "Regional Processor is being shut down".
After discussions on PMR 40488,311,75 and a parallel case with SWIFT, it is clear that SWIFT does not document this abort reason explicitely as to be automatically re-connected by the CBT. But SWIFT claims that is is "best practice" for a CBT to do so.
Therefore please review possilbe system abort cases and implement automatic re-connect/re-open of a session from CBT side as recommended by SWIFTs "best practices".
And if a re-connect is not possible, at least an error-event is needed to be reported by FTM/WBI-FN so that we can setup an alarm-chain.
In the current situation we were not even alerted as the system abort is just an informational event.
Ohterwise there are cases were SWIFTNet FIN LT sessions are "lost" without re-connect try and without error-notification.
Do not place IBM confidential, company confidential, or personal information into any field.