IBM Support

IT47943: SWIFTNET7 FILEACT EVENT MESSAGES SENT BY SWIFT WHILE B2BI ENCOUNTERING DB OUTAGE WILL NOT BE RESENT AFTER OUTAGE

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Problem Description:
    When B2BI encounters a database connection issue or other
    interruption that results in HTTP/S requests from MEFG to
    timeout, SWIFTNet7 messages sent by SWIFT via MEFG will be
    affected as well, resulting in the messages being resent by
    SWIFT.  However, SWIFTNet7 FileAct Event messages sent by SWIFT
    during this interval will not be resent.  This because SWIFT
    does not accept any response for Event messages.  This can
    result in files which were successfully received not triggering
    events which would pull the files from the MEFG system, when
    receiving the Completed Event message.
    
    Platforms Affected:
    All
    

Local fix

  • Resolution Summary:
    
    Added a new script, install_dir/etc/RecoveryFAEvent.sh which
    will allow customer to identify and resend failed Event messages
    for defined interval.
    

Problem summary

  • Users Affected:
    All
    
    Problem Description:
    When Sterling B2B Integrator encounters a database connection
    issue or other interruption that results in HTTP/S requests from
    MEFG to time out, SWIFTNet7 messages sent by SWIFT via MEFG will
    be affected as well, resulting in the messages being resent by
    SWIFT. However, SWIFTNet7 FileAct Event messages sent by SWIFT
    during this interval will not be resent. This is because SWIFT
    does not accept any response for Event messages. This can result
    in files that were successfully received not triggering events
    that would pull the files from the MEFG system upon receiving
    the Completed Event message.
    
    Platforms Affected:
    All
    

Problem conclusion

  • Resolution Summary:
    A new script install_dir/etc/RecoveryFAEvent.sh has been added.
    This script enables customers to identify and resend failed
    event messages within a defined interval.
    
    Delivered in:
    6020005
    All future Fix Packs can be found in the Release Timeline Matrix
    - https://www.ibm.com/support/pages/node/6194265
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT47943

  • Reported component name

    STR B2B INTEGRA

  • Reported component ID

    5725D0600

  • Reported release

    620

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2025-04-10

  • Closed date

    2025-06-18

  • Last modified date

    2025-06-18

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

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

Fix information

  • Fixed component name

    STR B2B INTEGRA

  • Fixed component ID

    5725D0600

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS3JSW","label":"Sterling B2B Integrator"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"620","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]

Document Information

Modified date:
18 June 2025