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

Obtain the fix for this APAR.

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 is sysrouted FROM one or more of the following:

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

  PM77813 UK91464

Modules/Macros

•    DNF10001 DNF10042 DNF10056 DNF10057 DNF10059
  

Publications Referenced

SH12693613

SH12693913

Fix information

• Fixed component name

  MS FOR SN IA AN

• Fixed component ID

  5655FIN02

Applicable component levels

• R11F PSY UK91464

     UP13/02/08 P F302

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.