This section explains the mechanism of data linkage from one HiRDB to another HiRDB.

When the source database is updated, the source Datareplicator extracts the update information (information used by the UAP to update the database) from the HiRDB's system log file and stores it in an extraction information queue file. This is called extraction processing. You can use a user own coding (UOC) routine to check the update information in order to determine whether to send it to the target Datareplicator.

The update information is sent to the target Datareplicator at the interval defined in the source Datareplicator and is stored in an import information queue file, from where it is imported into the target database in the transaction units defined in the target Datareplicator. This is called import processing. Note that this update processing at the target database is not synchronized with the update processing in the source database.

Update information can be imported into the target database by the target Datareplicator either automatically or at a time of your choosing by using a UOC routine. Figure 1-3 shows the mechanism of data linkage from one HiRDB into another HiRDB.

Figure 1-3 Mechanism of data linkage from one HiRDB to another HiRDB

#1

The source Datareplicator sends the data automatically.

#2

This UOC routine checks the update information, and then sends it.

#3

The target Datareplicator imports the data automatically.

#4

This UOC routine edits the update information, and then imports it.

#5

The target Datareplicator imports the data automatically. A UOC routine can be used to process the update information before importing it into the target database.

This section explains the mechanism of data linkage from a HiRDB to a mainframe database (XDM/RD E2).

When the source database is updated, the source Datareplicator extracts the update information from the HiRDB's system log file and stores it in an extraction information queue file. A UOC routine can be used to check the update information and determine whether to send it to the target Datareplicator.

The update information is sent to the XDM/DS data linkage product at the mainframe system at the interval defined in the source Datareplicator and is stored in the update information dataset. The stored update information is imported into the target database in the transaction units of the source database defined in XDM/DS. Note that this update processing at the target database is not synchronized with the update processing in the source database.

Update information can be imported into the target database by XDM/DS either automatically or at a time of your choosing by using a UOC routine. The following figure shows the mechanism of data linkage from a HiRDB to a mainframe database.

Figure 1-4 Mechanism of data linkage from a HiRDB to a mainframe database

#1

The source Datareplicator sends the data automatically.

#2

This UOC routine checks the update information, and then sends it.

#3

The target XDM/DS imports the data automatically.

#4

This UOC routine edits the update information, and then imports it.

This section explains the mechanism of data linkage from a mainframe database (XDM/SD E2, XDM/RD E2, ADM, PDMII E2, or TMS-4V/SP) to a HiRDB.

When the source database is updated, the XDM/DS data linkage product on the mainframe system extracts the update information and stores it in an update information dataset.

The update information is sent to the target Datareplicator at the interval specified by XDM/DS and stored in an import information queue file. The update information is then imported into the target database in the source database transaction units defined in the target Datareplicator. Note that update processing for the target database is not synchronized with update processing for the source database.

Update information can be imported into the target database by Datareplicator either automatically or at a time of your choosing by using a UOC routine.

The following figure shows the mechanism of data linkage from a mainframe database to a HiRDB.

Figure 1-5 Mechanism of data linkage from a mainframe database to a HiRDB

#1

One of XDM/SD E2, XDM/RD E2, ADM, VOS3 PDMII E2, or TMS-4V/SP is required. For TMS-4V/SP, the TMS-4V/SP/Data Linkage Support is required.

#2

The target Datareplicator imports the data automatically.

#3

This UOC routine edits the update interface, and then imports it.

#4

The source database is XDM/RD E2.

#5

The target Datareplicator imports the data automatically. A UOC routine can be used to process the update information before importing it into the target database.

A SAM file stores data sequentially from the beginning of the file. Datareplicator uses SAM files to link data in VOS1 PDMII E2 or VOS1 RDB1 E2. This subsection explains the mechanism of data linkage from a mainframe database (PDMII E2 or RDB1 E2) to a HiRDB using a SAM file.

When the source database is updated, the source Datareplicator extracts the update information on the basis of definitions in the mainframe system, and then stores it in a SAM file via the mainframe's update information dataset. This SAM file is then transferred in binary format to the target Datareplicator by one of the following file transfer programs:

VOS3 PDM2 E2

File transfer using VOS3 XFIT, XNF/TCP, or IFIT-TSS E2

VOS1 PDM2 E2 or VOS1 RDB1 E2

File transfer using VOS1 XFIT, HCAM/TCP, or IFIT/IEX

The directory used to store the SAM file in the target system depends on a specification for the file transfer program.

You must execute manually the target Datareplicator's update information input command (hdssamqin command) in order to store the update information from the SAM file into an import information queue file. The update information stored in the import information queue file is imported into the target database in the source database transaction units defined in the target Datareplicator. Note that this update processing at the target database is not synchronized with the update processing in the source database.

Update information can be imported into the target database by Datareplicator either automatically or at a time of your choosing by using a UOC routine. The following figure shows the mechanism of data linkage from a mainframe database to a HiRDB using a SAM file.

Figure 1-6 Mechanism of data linkage from a mainframe database to a HiRDB using a SAM file

#1

The target Datareplicator imports the data automatically.

#2

This UOC routine edits the update interface, and then imports it.

#3

To store update information from a SAM file into an import information queue file, use the Datareplicator's hdssamqin command (execute this command manually).

#4

The target Datareplicator imports the data automatically. A UOC routine can be used to process the update information before importing it into the target database.