Updating reference data

To ensure that reference data remains current after it was initially imported as described in Importing reference data for the first time, you must occasionally import more recent versions of the reference data.

Notes:

Because each delta package contains only those changes relative to the previous package, you cannot skip delta packages. However, if you miss a delta package, you can always obtain the most current data by importing the most recent full package, plus any subsequent delta packages.
The Directory packages are released by SWIFT before some of the data becomes active. If you try to import a BIC Directory 2018 bank file before its data is active, the import is rejected. If you are sure, you want to import the bank file before all data is active, issue the dnprdu command with the -future parameter. This confirms that you understand that the data in the database table is modified before those changes are active by SWIFT. See the command line description of RDU for more information.

To use the RDU to update the data reference tables:

Download the BIC Directory 2018, BankDirectoryPlus or SWIFTRef ReachPlus for FINplus directory package from SWIFT that contains the data to be imported.
Log on to z/OS® UNIX as a reference data administrator.
Run the copy of dniprofile that you created during the procedure described in Importing reference data for the first time:
```
. /var/ftmswift_v324/run/dniprofile
```
Import BIC Directory 2018 or BankDirectoryPlus data in one of the following ways:
Import all three types of data (bank, currency, and country) from a delta package with a single command
Issue the Reference Data Utility command command for the delta package, for example to import data from a BankDirectoryPlus delta package, that contains data that is not yet active:
```
dnprdu -file BANKDIRECTORYPLUS_20130804_TXT.zip
       -dir /u/download/SWIFT/ 
       -delta 
       -logpath /u/download/SWIFT/RDULogFiles/
       -future
```
The program automatically processes the files consecutively and writes three log files, one for each data file.
If the import of one data file fails, RDU imports the others. For information about how to manage a failed import, see Restarting a failed import.
Import each type of data (bank, currency, and country) from a separate delta text file by issuing a separate command for each type of data
Take the following actions:
1. Ensure that you have access to the individual file.
2. Issue the Reference Data Utility command command for each text file that is to be imported. For example, enter the following command to import a delta file:
  dnprdu -file FIDELTA_20100904.txt -dir /u/download/SWIFT/
  The program creates a new log file each time the dnprdu command is issued.
Import the SWIFTRef ReachPlus for FINplus data if FINplus remote address support is required.
Issue the Reference Data Utility command command for the delta package. For example to import data from a SWIFTRef ReachPlus for FINplus delta package, that contains data that is not yet active:
```
dnprdu -file REACHPLUS_V1_FINPLUS_MONTHLY_DELTA_20230324_TXT.zip
       -dir /u/download/SWIFT/ 
       -delta 
       -logpath /u/download/SWIFT/RDULogFiles/
       
```
After updating the reference data with a FULL file, it is recommended to run the Db2® runstats utility to update the catalog statistics for the reference data tables in the DNIBICI table space.
To make the updated data usable by FTM SWIFT, please see Activating reference data updates for message validation and Making reference data updates visible in MER and RMA enterprise applications.