To establish correspondence between a mainframe database that uses SAM files (PDM2 E2 or RDB1 R2) and a target Datareplicator, you must design the items discussed below. This section explains the specifications for the target Datareplicator.

(a) Proportion

There are no limitations on the ratio of mainframe databases to target Datareplicators. However, a single target Datareplicator can execute a maximum of 128 (UNIX Datareplicator) or 63 (Windows Datareplicator) update information input commands (hdssamqin) at one time.

If you run multiple target Datareplicators for one target HiRDB, you can receive update information from over 128 source systems (data linkage identifiers). However, when update information is imported from multiple target Datareplicators into a single target HiRDB (database), 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 the target Datareplicator, specify the data linkage identifier in the dsidxxx operand in the import system definition. Specify this data linkage identifier in the hdssamqin command.

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.

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.