Loading GPI confirmations

Note: Before performing any of the tasks described in this section, carry out the procedure described in Configuring the Sequential Data Facility.

Use the Sequential Data Facility (SDF) to load confirmation messages to ensure that SWIFT customer payments can be fully tracked. In order to facilitate this processing, SWIFT has defined a CSV file structure for payment confirmations. Files conforming to this specification can be loaded into FTM SWIFT using the Sequential Data Facility (SDF) which then creates MT199 messages and puts them on the specified IBM MQ input queue. Depending on subsequent processing, those MT199 message then will be sent to the network/SWIFT tracker.

The Sequential Data Facility (SDF) supports both the BASIC and ADVANCED CSV guidelines as described in the SWIFT Universal Confirmations CSV File Structure for Payment Confirmation of MT103 documentation. The CSV guidelines define UETR as optional element in the CSV files, but they are mandatory when loading the files using SDF. The destination BIC will be set to TRCKCHZZ for production and TRCKCHZ0 for Test&Training environments. The FIN sender address and transaction reference values can be set using the -fmtopt option. See the command description for details.

Ensure that the applications that provide the input data use the data formats described for BASIC or ADVANCED formats.
Check the pre-requisite options or variables depending on how SDF is carried out:
- Running on the command line
  
  Java home directory
  
  Locate the home directory of your Java 1.8 or later installation
  
  Data set support library
  
  Add the directory containing the JZOS support library for Java to your CLASSPATH:
  Example: export CLASSPATH=/local/java/J8.0_64/lib/s390x:$CLASSPATH
  
  IBM MQ Java™ library directory
  
  Add the IBM MQ Java libraries to the CLASSPATH.
  Example: export CLASSPATH=/usr/lpp/mqm/V9R1M1/java/lib/com.ibm.mq.jar:$CLASSPATH
  
  Path to FTM SWIFT installation directory
  
  Identify the path to the SDF code.
  Example: /usr/lpp/IBM/ftm/ftmswift/v324/run/classes
  
  The following example shows how the values can be specified when carrying out the SDF.
```
prompt> export CLASSPATH=/usr/lpp/mqm/V9R1M1/java/lib/com.ibm.mq.jar:
                         /local/java/J8.0_64/lib/s390x:$CLASSPATH
prompt> java
        -cp $CLASSPATH:/usr/lpp/IBM/ftm/ftmswift/v324/run/classes/CmdLineOpt.jar:
                       /usr/lpp/IBM/ftm/ftmswift/v324/run/classes/dni.xmlsupport.jar:
                       /usr/lpp/IBM/ftm/ftmswift/v324/run/classes/dnqcbsdf.jar
        com.ibm.dnq.sdf.DnqcbSdf
        -import my.csv 
        -queue ABC .... 
```
- Shell script dnqsdf
  Before issuing the dnqsdf command, you must have run your FTM SWIFT profile, for example:
```
. /var/ftmswift_v324/run/dniprofile
```
Run the import task (either directly using Java on the command line or through a shell script) as needed.

In the example below, SDF is executed using the shell script dnqsdf:

dnqsdf -import confirm.csv -ou OU1 -format CSV -fmtopt IBMADEFFAXXX;Myref%04d
-queue INST1.OU1.DNF_ILC_FIN -inst INST1

The MT199 messages will be created and stored in the INST1.OU1.DNF_ILC_FIN queue. The FIN sender address is set to IBMADEFFAXXX and the transaction reference will be generated using a running number within this import operation, starting with "Myref0001" and then incremented by one for the next messages.

Example of a generated MT199 message:

{1:F01IBMADEFFAXXX0000000000}{2:I199TRCKCHZZXXXXN}{3:{121:11111111-7a48-4f5c-b890-bb3bf47fffff}}{4:
:20:Myref0002
:21:Payment0123444
:79://2012011000+0100
//RJCT/DUPL
//BANKBEBBXXX
//EUR9500,
-}