IBM Support

IT10423: SWIFT STORE AND FORWARD RETRY POLICY ADHERENCE ENHANCEMENT

Direct link to fix

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as suggestion for future release.

Error description

  • SWIFT added new compliance requirements to add retry attempts
    for the primatives FetchFileReqest and AckSnFRequest.
    

Local fix

Problem summary

  • Problem Description:
    The SN7 SnF FA current implementation makes a single attempt to
    send a FetchFileReqest or AckSnFRequest request. If a
    transmission failure occurs, preventing SWIFT from receiving
    these requests, Sterling B2B Integrator will flag the BPs as
    in error and indicate
    the failure in the SWIFTNet Correlation tables. The pending SnF
    FA message that SWIFT is trying to send will not be sent and/or
    will be deleted by SWIFT.
    
    Platforms Affected:
    All
    
    Users Affected:
    SwiftNet users
    

Problem conclusion

  • Resolution Summary:
    A retry policy has been implemented for FetchFileRequest and
    AckSnFRequest primitives, sent by the FileAct SnF messaging
    interface, with the goal to reduce the delay in processing SnF
    messages held by SWIFT. This is accomplished through the
    automation of a resend of FileAct SnF primitives for up to a MAX
    RETRY count. The resend retry automation is performed by
    modifications to the SWIFTNet7FileActFetch and
    SWIFTNet7FileActNotification BPs and two new BPs,
    SWIFTNet7FileActFetchRetry and
    SWIFTNet7FileActNotificationRetry. The Retry BPs are initiated
    in the onFault condition, as a result of failures to transmit
    from MEFG to SWIFT.
    
    Delivered In:
    5020500_7
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT10423

  • Reported component name

    STR B2B INTEGRA

  • Reported component ID

    5725D0600

  • Reported release

    525

  • Status

    CLOSED SUG

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-08-04

  • Closed date

    2015-08-04

  • Last modified date

    2015-08-05

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS3JSW","label":"IBM Sterling B2B Integrator"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2.5","Edition":"","Line of Business":{"code":"LOB02","label":"AI Applications"}}]

Document Information

Modified date:
05 August 2015