import

Purpose

Parameters

-file filename

Name of the distribution file from which authorisations are to be imported. The broker must have read permission for this file.

-dir directory

The directory in which the distribution file is stored. The default is the directory specified by the DefaultImportDir attribute of the DnfRmParameters CO as described in Configuring default directories for RM and ASP data. The broker must have read permission for this directory.

-lkn lau_key

Name of the local authentication (LAU) key. This key is a CO of type DnfLAUKeyRM, as described in Configuring a LAU key to secure RM data.

-bl bic_list

To limit for which destinations authorisations are imported, specify a list of BIC8s, separated by commas. Only those records that include one of the BIC8s in the list as either issuer or correspondent are imported. If this parameter is not specified, authorisations for all BIC8s are imported.

-lf log_file

The name of the file to which the import log is to be written. If the file name is not fully qualified the specified file is stored in the default log directory that is configured as described in Configuring default directories for RM and ASP data. If no default log directory is configured the default is the home directory of the user ID of the broker started task. The broker must have write permission for the directory in which the log file will be stored. You cannot specify an existing log file. For more information about the contents of this file, see Checking the import log.

-lfd log_dir

The directory in which the log file is to be stored. The broker must have write permission for this directory. The default is the log directory that is configured as described in Configuring default directories for RM and ASP data. If no default log directory is configured the default is the home directory of the user ID of the broker started task. For more information about the contents of the log file, see Checking the import log.

When this parameter is specified, the name of the log file is generated automatically and has the form:

rm_import_ou_timestamp_number.log

where:

ou

The name of the OU for which the import command was issued.

timestamp

A timestamp of the form YYYYMMDDhhmmssnnnnnn that indicates when the import command was issued.

number

A number to ensure that the log files for import commands that are processed simultaneously have names that are unique.

For example, if an import command is issued for BANKA at 23:59:13.985472 UTC on 30 June 2010, and if no other import command is processed for this OU at the same time, the import log file is given the name:

rm_import_BANKA_20100630235913985472_1.log

-filemode

A distribution file that is to be imported can have one of the following modes:

complete

The data in the distribution file represents all authorisations for all the BIC8s listed in the <Sw:Bic8Lst> tag of the distribution file. Authorisations for all these BIC8s are deleted from the RM data store before the contents of the distribution file are imported.

Notes:

1. Partial distribution files are typically much smaller than complete distribution files, so you will probably prefer to work with them, and use complete distribution files only when you suspect that the relationship management data in the RM data store is corrupted.
2. When you import a file with the filemode complete, there is a time period during which the old records were deleted, but the new records were not yet created. If there is FIN or MSIF traffic during this period, some messages might not be able to be processed due to missing RM authorisations. Therefore, before importing a complete RM distribution file, stop all FIN and MSIF traffic, for example:
   • For FIN traffic, by issuing the quit command for each FIN LT, or by stopping the DNF_ILC_FIN message flow
   • For MSIF traffic, by issuing the stop command for each OU, or by stopping the DNF_O_FT message flow
3. Authorisations for all of the specified BIC8s are deleted from the RM data store before the contents of the distribution file are imported, including all bootstrap authorisations. Therefore, specify -filemode complete only if all bootstrap authorisations were already exported (that is, if the number of bootstrap authorisations that were not yet exported=0). To determine the number of bootstrap authorisations that were not yet exported, enter query -t summary as described in query.

partial

The data in the distribution file represents a subset of the authorisations for the BIC8s listed in the <Sw:Bic8Lst> tag in the header of the distribution file. No authorisations are deleted from the RM data store before the contents of the distribution file are imported. If the RM data store already contains a record that corresponds to a record in the distribution file, it is replaced only if the record in the distribution file is younger. This is the default.

The filemode you specify must correspond to the filemode specified for the <Sw:FileMaintncSts> tag in the header of the input distribution file; otherwise, the import command is rejected.

-trial

Specify this parameter to invoke import command in trial mode. In this mode, only the log file is written as report, but the data in RM data store is not changed. With this option, the effect of an import command can be checked without manipulating runtime data.