For details about the correspondence between the source database and XDM/DS, see the VOD3 XDM/DS manual.

To establish correspondence between XDM/DS and the target Datareplicator, you must design the items discussed below. This section explains the specifications for the target Datareplicator; for details about the specification of each XDM/DS item, see the VOS3 XDM/DS manual.

(a) Proportion

XDM/DS to target Datareplicators = 1 to m

XDM/DSs to target Datareplicator = n to 1

Variable	UNIX	Windows
m	For details about the range of m, see the manual VOS3 XDM Data Linkage Facility XDM/DS Description and Definition.
n	1 to 128	1 to 63

There can be multiple target Datareplicators per XDM/DS. This means that you can send update information from a single XDM/DS to multiple target Datareplicators.

On the other hand, one target Datareplicator can receive update information from multiple XDM/DSs.

If you run multiple target Datareplicators for one target HiRDB, you can receive update information from 128 or more (in Windows, 63 or more) source systems (data linkage identifiers). However, the following problems might occur:

• Import processing might result in lock errors.
• The order in which the update information is imported might not be as expected.

(b) Data linkage identifiers

For details about the data linkage identifiers, see 4.4.1(2)(c) Data linkage identifiers.

(c) Target Datareplicator identifiers

The identifier used to identify a target Datareplicator is called a target Datareplicator identifier. Specify a target Datareplicator identifier in the hdsid operand in the import system definition.

At the source Datareplicator, use the sendhdsid operand in the transmission environment definition to specify the target Datareplicator identifier at the destination of the update information.

(d) Communications protocol

To transfer update information between XDM/DS and a target Datareplicator, you must specify the communications protocol. For the target Datareplicator, specify the protocol1 or protocol2 operand in the import system definition.

(e) T-selector

To transfer update information between XDM/DS and a target Datareplicator using the OSI protocol (channel connection), you must specify a T-selector. For the target Datareplicator, use the reflect_tselector operand in the import system definition.

(f) Service name

To transfer update information between XDM/DS and a target Datareplicator using the TCP/IP protocol, you must add the communication service name in the following services file:

• UNIX Datareplicator: /etc/services
• Windows Datareplicator: Windows-system-directory\drivers\etc\services

Specify the applicable communication service name in the target Datareplicator's hdsservices operand.

For details about the correspondence between the target Datareplicator and the target HiRDB, see 4.4.1(3) Correspondence between target Datareplicator and target HiRDB.