Designing data linkage from a HiRDB to a mainframe database

In designing data linkage from a HiRDB to a mainframe database (XDM/RD E2), the correspondence between the source and target systems depends on whether the source HiRDB is a single server or a parallel server.

Figure 4-18 shows the correspondence when the source HiRDB is a single server, and Figure 4-19 shows the correspondence when the source HiRDB is a parallel server.

Figure 4-18 Correspondence between the source and target systems in designing data linkage from a HiRDB to a mainframe database: Source HiRDB is a single server

[Figure]

Figure 4-19 Correspondence between the source and target systems in designing data linkage from a HiRDB to a mainframe database: Source HiRDB is a parallel server

[Figure]

Organization of this subsection: (1) Correspondence between source HiRDB and source Datareplicator; (2) Correspondence between source Datareplicator and XDM/DS; (3) Correspondence between XDM/DS and target database

You design the items discussed below to establish correspondence between the source Datareplicator and XDM/DS. This section explains the specifications for the target Datareplicator; for details about the specifications of the XDM/DS items, see the manual VOS3 XDM Data Linkage Facility XDM/DS Description and Definition.

(a) Proportion

Source Datareplicator to XDM/DSs = 1 to m

Source Datareplicator to XDM/DS = 1 to 1

Variable	UNIX	Windows
m	1 to 64^#	1 to 63^#

#: If sendmst is specified in the sendcontrol operand, the value range is 1 to 4,096.

You can send update information from a single source Datareplicator to multiple target XDM/DSs. If the HiRDB is a parallel server, you can send update information to multiple target XDM/DSs per source Datareplicator at a server containing a back-end server.

On the other hand, one target XDM/DS can receive update information from only one source Datareplicator. If you run multiple XDM/DSs for one target XDM/DS, you can receive update information from multiple 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) Target identifiers

For details about target identifiers, see 4.4.1(2)(b) Target identifiers.

(c) Data linkage identifiers

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

(d) Source Datareplicator identifiers

The identifier used to identify a source Datareplicator is called a source Datareplicator identifier. Specify a source Datareplicator identifier in the hdeid operand in the extraction system definition.

(e) Target identifiers

For details about specifying target identifiers in XDM/DS, see the manual VOS3 XDM Data Linkage Facility XDM/DS Description and Definition.

(f) Service name

To transfer update information between source and target Datareplicators, you must add the name of the communications service in the following services file:

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

Specify the name of the applicable communications service in the hdeservice operand in the transmission environment definition for the source Datareplicator.

(g) Host name

To send update information, you must register the host name in the following hosts file at the source system:

UNIX Datareplicator: /etc/hosts
Windows Datareplicator: Windows-system-directory\drivers\etc\hosts

Specify the host name in the hdehost operand in the transmission environment definition.

4.4.2 Designing data linkage from a HiRDB to a mainframe database

(1) Correspondence between source HiRDB and source Datareplicator

(2) Correspondence between source Datareplicator and XDM/DS