WebSphere BI for FN tolerates SWIFTNet 6.3

News


Abstract

WebSphere Business Integration for Financial Networks V2.2 and V3.1 products support the optional SWIFTNet 6.3 release 'in toleration mode without SAG Add-On', that is, SAG 6.3 can be used instead of SAG 6.0 or 6.1 without exploiting any of its new functions.
However, problems with SAG 6.3 were experienced and work on a solution is ongoing.
APAR PK90922 (DNFN2602E, DNFO9501E, DNFO1021E error events occurred due to the Restart SAG signal for SWIFT 6.3 ) has been opened for the EFAS service.
Further investigations show that the problems experienced in the DIAS service can be ignored, and that no problems were detected in the EIAS services.
APAR PK93264 titled "ERROR EVENT DNFF4400E DURING THE SAG 6.3 RESTART AND FSM HANG DUE TO THE SEGMENT VIOLATION " has been opened in the FIN area. The problem occurs when the LT is active and a SAG restart message is issued.
An update will be provided as soon as a solution is available.

Content

The compatibility of the current WebSphere BI for FN V2.2 and V3.1 products with the SWIFTNet 6.3 release was tested. The current WebSphere BI for FN V2.2 and V3.1 products support the optional SWIFTNet 6.3 release 'in toleration mode without SAG Add-On', i.e. SAG 6.3 can be used instead of SAG 6.0 or 6.1 without exploiting any of its new functions.

'Toleration mode without SAG Add-On' means that FIN, EIAS, DIAS, and EFAS functionality will work with SAG 6.3 release, but DFAS, SAG Configuration, and SAG Operation will not work with SAG 6.3 release.

Note: It is especially important for customers using SAG Add-On functionality for automating their operation (e.g monitoring of SAG events and show them in SYSLOG) that it will not work with SWIFTNet 6.3 release.

However, problems with SAG 6.3 were experienced and work on a solution is ongoing.
APAR PK90922 (DNFN2602E, DNFO9501E, DNFO1021E error events occurred due to the Restart SAG signal for SWIFT 6.3 ) has been opened for the EFAS service. The error events occur due to the restart SAG signal, which was changed in SAG 6.3 and contains a payload with additional information. The systems should still be operational. A possible workaround is to perform the subscribe -snlid command for SAG as described for event DNFO1040I in "WebSphere BI for FN Messages & Code". The problem will be solved within the PTF UK48785 for APAR PK90922.

Further investigations show that the problems experienced in the DIAS service can be ignored, and that no problems were detected in the EIAS services.

APAR PK93264 titled "ERROR EVENT DNFF4400E DURING THE SAG 6.3 RESTART AND FSM HANG DUE TO THE SEGMENT VIOLATION " has been opened in the FIN area. The problem occurs when the LT is active and a SAG restart message is issued. The problem will be solved within the PTF UK49340 for APAR PK93264.


Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Business Integration for Financial Networks
Documentation

Software version:

2.2, 3.1

Operating system(s):

Multi-Platform, z/OS

Reference #:

1392189

Modified date:

2009-08-11

Translate my page

Machine Translation

Content navigation