PI41667: SENDFILE TRANSFER SHOULD'T GO INTO ERROR_NOTIF, IF NO SAG SUBSCRIPTION, AND DELIVERY NOTIFICATION RECEIVED SUCCESSFULLY

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When a subscription to the SAG gets lost, File transfer events
  can no longer be received by MSIF.
  A transfer in state responded won't receive the events which
  bring it to state accepted and TranferComplete, though the file
  transfer was completed on the SAG and the file was received by
  the counterparty.
  Instead, the transfer gets a timeout and goes into Error state,
  even if a delivery notification has been received from the
  counterparty and has already been responded successfully.
  
  This behaviour makes no sense from a business point of view;
  when a delivery notification has been processed successfully for
  a SendFile request which has been responded from the SAG, the
  transfer should be marked as completed, and a positive response
  should be passed to the application.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: SENDFILE TRANSFER SHOULD'T GO INTO      *
  *                      ERROR_NOTIF, IF NO SAG SUBSCRIPTION     *
  *                      AND DELIVERY NOTIFICATION RECEIVED      *
  *                      SUCCESSFULLY                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  After MSIF initiates a SendFile transfer it expects to receive
  status events from the SAG that indicate the progress of the
  file transfer to the receiver. If subscriptions to receive
  SAG status events have been lost on the SAG, then the SAG
  does not send such events and MSIF is not informed of the
  successful completion of a transfer. If for a SendFile
  transfer MSIF requested from the receiver a delivery
  notification, then there might be a scenario where no
  SAG status events are received but a successful delivery
  notification of the file is received.
  Formerly, MSIF treated this scenario as an error because no
  SAG status event is received that indicated a successful
  transfer of the file.
  

Problem conclusion

• Now, MSIF treats this scenario as success because the delivery
  notification indicates that the receiver received the file
  successfully.
  

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:

  PI41934

Modules/Macros

• DNF10056
  

Fix information

• Fixed component name

  MS FOR SN IA AN

• Fixed component ID

  5655FIN02

Applicable component levels

• R11F PSY UI31384

     UP15/09/26 P F509

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.