RDU log and trace files

Each time the dnprdu command is issued, it creates the following files:

One log file for each imported bank, currency and country file. Each log file contains information about the data that the RDU processed. The files are stored in the directory specified for the -logpath parameter or, if this parameter is not specified, in the current directory. Each log file has a name of the form:
```
RDU_xx_yyyymmdd_hhmmsssss.log
```
where:

xx

A two-letter abbreviation indicating the type (FI, B3, CU, or CT) of the imported file to which the log file applies.

yyyymmdd

The year, month, and day on which the log file was written.

hhmmsssss

The time, in hours, minutes, and milliseconds, at which the log file was written.
One trace file, if the parameter -trace is set, which records each RDU processing step, and is used to diagnose errors. If a DNF_CONFPATH environment variable is set and points to a correct DNI.CONF file, then the trace path is taken according to the definitions in this file. If not existing, the default trace path will be "/var/ftmswift_v300/run/trace/". If this path does not exist or the program cannot create the trace file there, it will store the trace in the current directory. The trace file has a name of the form:
```
RDU_yyyymmdd_hhmmsssss.trc
```

It creates these files regardless of whether the command was issued for a package (.zip file) or a core data file (.txt file).

The following example shows an excerpt from a typical log file of an importing of a BIC directory ZIP file.

Import file name: FI_20151101.TXT
            from: /home/refdataadmin/BICDIR_BICDB_FULL_20151101.zip
Start date/time.: 2015-11-22, 21:20:39
Activation date.: 2015-11-01

PARAMETER USED
  -old
  -force
  -trace ALL
  -records   ubic

SUMMARY FILE OPERATION
  Import file type...: FI
  Import file version: FULL
  Input file contains 101982 rows.

  Modification Flag 'A': 522
  Modification Flag 'M': 592
  Modification Flag 'U': 100672
  Modification Flag 'D': 196
...

The log file records the parameters that were specified in the PARAMETER USED section and displays information about the number of records in the input file together with each type of modification flag:

A: Addition
M: Modification
U: Unchanged
D: Deletion

The SUMMARY FILE OPERATION section in the log will contain information of records which cannot be processed (error in length, incorrect fields etc.), as shown in the following picture.

...
SUMMARY FILE OPERATION
  Import file type...: FI
  Import file version: FULL
  Input file contains 21 rows.
  2 rows are not valid.
   Row 000014 of import file invalid --> Invalid record identifier
   Row 000015 of import file invalid --> Invalid record format
...

If the parameter -logdetails is used, a log file entry is written for each record identifying the operation performed as shown in the following picture.

...
SUMMARY DATABASE OPERATION
  Cleanup of 101786 records from database table

  ----------+--------------+--------------+-----------------------------------
  Database  | BIC Record   | Input file   | BIC
  Operation | KEY          | Flg    Row   | CODE
  ----------+--------------+-----+--------+-----------------------------------
  *LOCKED*  |  AAAARSBGXXX |  A  | 000001 | AAAARSBGXXX
  INSERTED  |  AAACKWKWXXX |  U  | 000002 | AAACKWKWXXX
  INSERTED  |  AAADFRP1XXX |  U  | 000003 | AAADFRP1XXX
  DELETED   |  AFXLGB2LXXX |  D  | 000004 | AFXLGB2LXXX
...

The end of the log file contains the summary of operations performed in the database:

...
  Records inserted: 19502
  Records updated:  13
  Records locked:   1
  Records deleted:  0
  Records not found for deletion: 44

LOAD COMPLETED SUCCESSFULLY

These fields show:

Record inserted: The number of records with modification flag A or M that were not yet in the database and where inserted.
Records updated: The number of records with modification flag M that were already in the database.
Rejected: The number of records with modification flag A, M, or D that were rejected because they did not have a (unique) BIC or because their structure was invalid and therefore did not fulfill the insertion criteria.
Records Locked: The number of records with modification flag M or D that were locked, that is, for which WRITE_PROTECTED='Y' was set.
Records Deleted: The number of records with modification flag D that were deleted from the database.
Not found for deletion: The number of records with modification flag D that were not found in the database.