Reference Data Utility command

Purpose

This section describes the Reference Data Utility (RDU) utility. The tool can be used to update the information in the reference database.

Before issuing the dnprdu command, run the profile dniprofile in the current shell.

Parameters

-file filename

Name of the input file:

• The name of a file that contains the SWIFT BICDirectory/BIC Directory 2018 or BankDirectoryPlus data, for example:

  FI_20151125.txt

• The name of a SWIFT BICDirectory/BIC Directory 2018 or BankDirectoryPlus archive, for example:

  BANKDIRECTORYPLUS_V3_FULL_20150828.zip

The filename cannot contain wildcard characters.

-dir directory

The directory in which the data file is located. The default is the current directory.

-locked

Force locked records to be updated - that is, records which are marked WRITE_PROTECTED='Y' in the database.

-old

Force an old data file to be imported.

-future

This parameter forces a data file to be imported even if its activation date lies in the future. This will cause the reference database to contain changes that might not yet be active in the SWIFT environment.

-delta

The BankDirectoryPlus and BIC Directory 2018 directory archives contain both FULL and DELTA bank files. The default behavior is to import the FULL file. This parameter can be used to override this behavior and import the DELTA file from the archive.

-records

This parameter determines which records are to be imported or updated:

ubic (default value)

Import or update only unique records:

• For BankDirectoryPlus, these are records that, in the B3 update file, identify a BIC.
• For Bic Directory and BIC Directory 2018, all records are unique so the -records parameter has no effect.

If the information is to be used only by RMA to obtain BIC details and to identify stale authorisations, or by the MER Facility to create drop-down lists of BICs, specify this value to reduce the amount of space required by the reference data in the database.

all

Import or update all records in the BI or B3 update file, regardless of whether they are unique.

-force

If an RDU process is already running when the command is issued, a second process refuses to start. However, when a RDU process ends abnormally, a subsequent process might believe that the previous process is still running. In such a situation, use the -force parameter. Before issuing this command, make sure, no other RDU process is still running.

-logpath path

Directory in which the log file is to be stored. The default is the current directory.

-trace level

The trace level, which determines the type of trace information that is recorded in a file. A lower level includes the information of all higher levels.

SEVERE

Error messages are recorded. This is the highest trace level.

WARNING

Warning information is recorded.

INFO

Informational messages are recorded in the trace.

FINE

Some debugging information is recorded.

ALL

The maximum amount of debugging information is recorded. This is the lowest trace level.

-dsn data source name

The data source to be used. If no -dsn option is used, the value of the DNI_DSN environment variable will be used as data source instead.

-schema schema name

The database schema for the reference data to be used. If no -schema option is used, the value of the DNI_SN environment variable will be used as schema name instead.

-uid user ID

Use the -uid option to specify a particular user that is used to connect to the reference database. The program will prompt for a user if required and not specified.

-pw password

Use the -pw option to specify the password for the user on the command line. Note that the password is visible and should be used only together with other security measures. For improved security, a stashed password file can be used. Specify the password in the format @stashfile to use the stash file containing the password, where stashfile is the path and file information for the stash file to be used.

If the password is not specified, the program will prompt the user if a password is required to access the reference database.

-progress

The option -progress can be used to display progress information during long running operations. The default is not to display progress information (dots).

-logdetails

The -logdetails option enables the detailed information of the performed operations in the log files. If not used, then only summary information will be included in the log file. The default is not to include detailed information about the records inserted/updated/deleted or unchanged in the log file.

-help or -?

Show help text that describes the most common parameters.