Manual procedure

This procedure must be executed individually for each LT that was active at the time of the event.

  1. Analyze the undelivered message report delivered by the SIPN after the SWIFTNet FIN cold start. The undelivered message report might consist of several output messages (OSNs) of message type 082 (Undelivered Message Report at Fixed Hour):
    • Ensure that all segments of the report are available.
    • Field 202 contains the actual segment number of a message.
    • Field 203 contains the total number of segments.
    • The GMT date and time of the report are shown in field 171 and 175.
  2. Scan all fields 335 in the report to find the oldest undelivered message.
  3. Extract the messages to be examined from the FTM SWIFT audit log: 
     select AM_LOG_GMT_TS, AM_BODY_CCSID, AM_MSG_GRP_ID, AM_NODE, AM_BODY
 from name.DNI_A_MSG_ou
                  where AM_LOG_GMT_TS >= starttime
                  and AM_LOG_GMT_TS < endtime
                  and AM_MSG_FLOW = ltname
                  order BY AM_LOG_GMT_TS
    where:
    starttime
    The starttime is input time of the oldest undelivered message, converted to GMT, plus five minutes. (The extra five minutes are to ensure that the audit log entry for the send-event is included.)
    endtime
    If the undelivered message report data was extracted before and is available, the endtime is the time of the last message before the SWIFTNet FIN cold start. Otherwise, extend the endtime to include the receive time of the undelivered message report.
  4. Determine the most recent undelivered message report. There might be a undelivered message report in the audit log that is more recent than the one delivered by the SIPN after the restart. The possible undelivered message reports are:
    066
    Undelivered Message Solicited Report.
    082
    Undelivered Message Report at Fixed Hour.
    083
    Undelivered Message Report at Cut-Off Time.
  5. Extract all outbound (ISN) messages from the set of messages. The AM_NODE column value is DnfFINISNSnffsm, the AM_BODY_CCSID should be 1047, that means the message body is in EBCDIC. The messages should start with characters {1:F01 to indicate a financial message. The data for further analysis is the basic header (block 1) and the service code field (103) in the user header.
  6. Extract all acknowledgments and reconcile these with the ISN messages. The body of an acknowledgment starts with characters {1:F21. The input time of the original ISN can be extracted from field 177 in the acknowledgment body. A possible NAK is indicated by characters {451:1} in the body. The reconciliation of ACKs is done based on the session and sequence numbers in the basic headers of the input message and of the acknowledgment.
  7. Extract delivery information from the audit log and reconcile with the ISN messages. The AM_NODE DnfFINOSNSnffsm column indicates an OSN or an OSN ACK. Check all messages starting with '{1:F01' and containing a block {2:O. In block 2 the three-digit message type is indicated. For message types 011, 015, and 019 this can be considered as a delivery notification or rejection. ISNs already delivered or rejected need not to be resend.
  8. For each ISN message in the message set, drop the message if any of the following conditions are met:
    • Its body does not start with the characters {1:F01.
    • It is a system message with a message type starting with 0.
    • The service code in the user-header field 103 of the message indicates that the message should not be resent. For information about the service codes, refer to the FINCopy service provider.
    • No acknowledgment for the message was received.
    • A negative acknowledgment was received. A field {451:1} in the body of an acknowledgment indicates that it is a negative acknowledgment.
    • An acknowledgment was received, its timestamp specifies an input time that is earlier than the timestamp in the report, and the MIR of the message is not listed in the undelivered message report, drop the message. Note that the input time in the acknowledgment is the local time of the sender, whereas the report timestamp is in UTC.
    • A related delivery or abort report message of type 011 or 019 was received. Such a message indicates that the ISN message was delivered or finally rejected.
  9. Before resending the remaining messages, for each message calculate a PDE based on the information in the ACK and add it the trailer (block 5) of the message. The PDE must contain the input time and input date (extracted from field 177) and the MIR of the message (extracted from the basic header of the corresponding ACK). 
    ACK: {1:F21ttttttttttttssssssssss}{4:{177:yymmddhhmm}{451:0}}
PDE: {PDE:hhmmyymmddttttttttttttssssssssss}