PM77813: MISSING ACK RESPONSE IN FILEACT SNF RECEIVE MUST NOT LEAD TO NOTIFICATION STATE "FAILED"

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When for a FileAct SnF Receive request the ACK response was not
    received in time, the tranfer itself completes successfully,
    however, the notification phase ends with notification state
    failed.
    This is because autorecovery re-sends the ACK and SWIFT returns
    a response, which indicates, that the ACK has already been
    received. This response is currently treated as a failure,
    though it should lead to completion of the notification phase
    (state: complete).
    The user himself must never get the impression, that he could do
    a manual recover for such a situation.
    In addition, SA, API and potentially CC guide need to
    be improved. Currently, the description of the notification
    phase is not clear - customer could derive, that the
    notification phase is only to handle delivery notifications,
    though also other processing is done during the notification
    phase.(and delivery notifications are not present for FileAct
    SnF Receive at all).
    The documentation needs to describe, what is done during the
    notification phase for the different scenarios, and it needs to
    distinguish between real time and SnF.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: MISSING ACK RESPONSE IN FILEACT SNF     *
    *                      RECEIVE MUST NOT LEAD TO NOTIFICATION   *
    *                      STATE "FAILED"                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Formerly, when MSIF failed to receive in time SWIFT's response
    to an ACK of an SnF FileReceived scenario, MSIF re-sent the
    ACK which led to an error response containing error code
    Sw.SnF.InvalidSnFRef. This error caused MSIF to change the
    notification state to 'Failed'.
    

Problem conclusion

  • Now, on receiving error code Sw.SnF.InvalidSnFRef for the
    FileReceived scenario, MSIF changes the notification state from
    'Sent' to 'Complete' as the provided error code indicates that
    the corresponding FileReceived scenario has already been
    acknowledged.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM77813

  • Reported component name

    MS FOR SW IA AN

  • Reported component ID

    5724D9633

  • Reported release

    311

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-11-27

  • Closed date

    2013-03-07

  • Last modified date

    2013-03-07

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

    PM77310

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

Fix information

  • Fixed component name

    MS FOR SW IA AN

  • Fixed component ID

    5724D9633

Applicable component levels

  • R311 PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Business Integration for Financial Networks

Software version:

311

Reference #:

PM77813

Modified date:

2013-03-07

Translate my page

Machine Translation

Content navigation