IBM RegTech Ideas Portal

 Welcome!

 

Our team welcomes any feedback and suggestions you have for improving our offerings. This forum allows us to connect your product improvement ideas with IBM product and engineering teams.

 

For product documentation, see Knowledge Center.
Create and View Support Cases and Use the Discussion Forum here

 

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

 

The shorter URL for this site is:   http://ibm.biz/WFS-Ideas

IBMers, please visit the WFSS Internal Ideas portal https://ibm.biz/WFS-Internal-Ideas

 

note: The IBM ICM IDEAS Portal is no longer available at this location. If you have reached this page, please look for a new link in the Varicent Administrator. Direct links are found under the "?" in the upper right corner.
A period of transition is likely to impact this service, while ICM becomes Varicent. Please contact Varicent support if you have additional challenges or concerns.

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.
  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Apr 9 2019
  • Future Consideration
Component Technology Stack Support (OS, Middleware, Protocols)
Priority High - Critical
  • Attach files