Reference Data Utility command

Purpose

The Reference Data Utility (RDU) 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 BIC Directory 2018 or BankDirectoryPlus data, for example:

  FI_20191125.txt

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

  BANKDIRECTORYPLUS_V3_FULL_20200828.zip

• The name of a SWIFTRef ReachPlus for FINplus directory archive, for example:

  REACHPLUS_V1_FINPLUS_MONTHLY_FULL_20230324_TXT.zip

• A SWIFT directory file received via FileAct. In this case, the CU, CT, B3, and FI formats are supported. For example, the following name specifies a currency code file (CU) in ZIP format:

  CURRENCY_CODE.zip

  Use the -Dcom.ibm.dnp.rdu.ignorePkgCheck=YES command line option to ignore the DNPR2153E error message.

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 by 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 causes the reference database to contain changes that might not yet be active in the SWIFT environment.

-delta

The BankDirectoryPlus, 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 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 could assume that the previous process is still running. In such a situation, use the -force option. Before using this option, make sure that 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 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

Specifies information about the connection to Db2®. Use one of the following notations:

• Db2_location_name
• //server:port/Db2_location_name

where:

Db2_location_name

The Db2 location name (for example, DNIDB)

server

The hostname or IP address of the Db2 server (for example, localhost)

port

The port of the Db2 subsystem (for example, 50000)

Only the second notation allows to use passwords longer than 8 characters.

If you do not specify this parameter, the first notation is used with the value of the environment variable DNI_DSN as Db2 location name.

-schema schema

The database schema for the reference data to be used. By default, the value of the environment variable DNI_SN is used.

-uid user ID

Use the -uid option to specify a particular user that is used to connect to the reference database. The program prompts 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 prompts for the password if it is required to access the reference database.

-progress

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

-logdetails

The -logdetails option causes detailed information about the performed operations to be written to the log file. If not used, only summary information is included in the log file. By default, the log file does not contain detailed information about the inserted, updated, deleted, or unchanged records.

-ssid subsystem ID

Use the -ssid option to specify a particular Db2 subsystem to be used by the reference data utility. This could be used, for example, if the default system wide subsystem ID is different from the one used for the reference database.

-help or -?

Show help text that describes the most common parameters.

Return codes