Explanation of the operands

dsid=data-linkage-identifier
~ <hexadecimal> ((00-FF)) <<00>>
Specify the data linkage identifier that will enable the target system to identify the source of the update information. This data linkage identifier must be unique in the corresponding target system.
qufile001="extraction-information-queue-filename"
~ <[pathname/]filename of 1-64 bytes> <<$HDEPATH/qufile001>>
qufile002="extraction-information-queue-filename"
~ <[pathname/]filename of 1-64 bytes> <<$HDEPATH/qufile002>>
:
qufile016="extraction-information-queue-filename"
~ <[pathname/]filename of 1-64 bytes> <<$HDEPATH/qufile016>>
Specify the names of the extraction information queue files, as absolute or relative pathnames. If you specify a relative pathname, Datareplicator assumes $HDEPATH/relative-pathname as the absolute pathname. The source Datareplicator adds _server-name to the specified name and creates a file under this filename. For UNIX, if the file is a character special file, you must create a file with the specified name to which _server-name is appended.
If you specify an absolute pathname, the complete filename including _server-name must not exceed 64 bytes. If you specify a relative pathname, the assumed absolute pathname plus _server-name must not exceed 125 bytes. This filename must be unique in the source system. If the source HiRDB is a parallel server, the filename must be unique within the back-end server.
Datareplicator uses file swapping to store information in the extraction information queue files. Therefore, you must provide at least two extraction information queue files; the maximum is 16 files. If you do not specify any extraction information queue filenames, Datareplicator assumes $HDEPATH/qufile001 for qufile001 and $HDEPATH/qufile002 for qufile002.
You must specify the qufile001 to qufile016 operands consecutively in ascending order beginning with qufile001. If they are not consecutive or in ascending order, Datareplicator stores update information in only those extraction information queue files that are specified consecutively in ascending order from the beginning. Datareplicator swaps the files in the order of their specification in this operand.
queuesize=extraction-information-queue-file-size
~ <unsigned integer> ((33-1000000000)) <<65>> (KB)
Specify the file size of the extraction information queue files specified with the qufile001 to qufile016 operands. The size specified in the queuesize operand applies to each of the files specified with the qufile001 to qufile016 operands.
For details about the formula for determining the size of an extraction information queue file, see 4.6.8 Designing the source Datareplicator's resources.
If you handle the extraction information queue files as large files, specify at least 2097152 (2 GB). To handle large files, you must already have set the OS and Datareplicator file system areas to support large files. For details, see 6.11 Handling of large files.

Note:

If you change the size of an existing extraction information queue file, you must initialize the source Datareplicator. Therefore, before you change file sizes, make sure that replication has been completed.
logiosize=system-log-I/O-buffer-size
~ <unsigned integer> ((32-510)) <<510>> (KB)
Specify the size of the system log I/O buffer that is used to read update information from the source HiRDB's system log. The actual buffer size is determined by the following formula using this operand:
4 x logiosize/4
For details about the size of the system log I/O buffer, see 4.6.3 Designing the extraction procedure.
quiosize=extraction-information-queue-I/O-buffer-size
~ <unsigned integer> ((32-510)) <<32>> (KB)
Specify the size of the extraction information queue I/O buffer that is used to store update information in the extraction information queue file or to read update information from the extraction information queue file. For details about the size of the update information queue I/O buffer, see 4.6.3 Designing the extraction procedure.
extsuppress=true|false
Specify whether to use of the source Datareplicator for a server that contains no tables subject to extraction processing is to be suppressed. The extsuppress operand is applicable only when the source HiRDB is a parallel server. Specify true to reduce the workload at a server that contains no tables subject to extraction processing. To ignore whether each server contains tables subject to extraction processing, specify false. For details about the specification of the extsuppress operand and the source HiRDB and source Datareplicator processing, see 6.5.4 Processing at the source HiRDB and source Datareplicator depending on the specification of extsuppress in the extraction environment definition.

true

The source Datareplicator is not to operate at a server that contains no tables subject to extraction processing. This means that no update information will be extracted from such a server even if a table it stores is specified in an extraction definition.

false

The source Datareplicator is to operate at all servers, including servers that contain no tables subject to extraction processing. If any server contains a table that is specified in an extraction definition, Datareplicator will extract update information from that table. If no table stored at a particular server is specified in an extraction definition, Datareplicator will not extract update information at that server. If you specify false and continue executing the HiRDB Datareplicator linkage facility with only the source HiRDB and without starting the source Datareplicator, the system log file might become full even though a corresponding server contains no tables subject to extraction processing.
ext_wait_interval=extraction-restart-interval-after-detecting-end-of-extraction
~ <unsigned integer> ((100-60000)) <<5000>> (milliseconds)
Specify the interval after which extraction processing is to be restarted once the end of update information sent from a DBMS subject to extraction processing is detected.
By specifying a small value in this operand, you can improve the spontaneity of extraction processing, because there is only a brief wait after the end of the system log file is detected. However, this might have an adverse effect on performance, because the CPU utilization factor increases. You need to take into account the frequency of update processing and CPU performance when specifying this value.
extract_level= current_gen|original_gen|all_gen
Specify the extraction level when the source HiRDB uses the inner replica facility.

current_gen

If the source HiRDB uses the inner replica facility, extract only the updates to the current RDAREA.

original_gen

If the source HiRDB uses the inner replica facility, extract only the updates to the original RDAREA.

all_gen

If the source HiRDB uses the inner replica facility, also extract the updates to all replica RDAREAs (including the original RDAREA).
int_trc_getv=true|false
Specify whether activity trace information is to be collected for extraction-related processes at this node (commondef common definition section) or back-end server (besdef individual definition section).

true

Collect activity trace for each extraction-related process.

false

Do not collect activity trace for each extraction-related process.

This operand is applicable only when nc is specified in the second parameter of the int_trc_lvl operand in the extraction system definition.
qufullwarn=extraction-information-queue-file-full-warning-value
Specify this operand to issue a warning message before the extraction information queue file becomes full. When the number of available extraction information queue files becomes equal to or less than the value specified here, Datareplicator issues a warning message. When this value is equal to or greater than the number of extraction information queue files, Datareplicator issues a warning message each time the extraction information queue files swap.
extract_delay_limit_time=extraction-delay-period-threshold
~ <unsigned integer> ((0-86400)) <<0>> (seconds)
Specify the threshold value for the difference (extraction delay period) between the time at which update information is stored in the system log file and the time at which the extraction information is written into the extraction information queue file. Whenever the actual extraction delay period exceeds the threshold value specified here, a warning message is output.
You must take into account the delay period also when you specify the ext_wait_interval operand in the extraction environment definition. If you specify a value of 0, the delay monitoring facility is disabled for extraction processes.

Note:

Adjust the value of this operand, taking into account the amount of update information subject to replication, the transmission interval, and the import interval. A recommended guideline value to start with is 10 minutes (600 seconds).

device01=Datareplicator-file-system-area-name[[,allocation-file-type] ...]
~ <absolute pathname of 1-125 bytes>
device02=Datareplicator-file-system-area-name[[,allocation-file-type] ...]
~ <absolute pathname of 1-125 bytes>
:
device18=Datareplicator-file-system-area-name[[,allocation-file-type] ...]
~ <absolute pathname of 1-125 bytes>
Specify the names of the Datareplicator file system areas and the file types to be allocated in each file system area. Specify a two-digit sequence number for xx in devicexx. The following table shows the correspondence between files and the file types to which they are allocated:

Allocation file type	File name to be specified in each operand
qufilexxx (xxx: integer from 001 to 016)	Link file name for extraction information queue file that was specified in set qufilexx. The server name is assigned to a created link file.
hde_file	Link file name for the corresponding back-end server's data linkage file.
sts_file	Link file name for the corresponding back-end server's status file.

If you do not specify any allocation file types, all files at the corresponding back-end server become subject to allocation. When a file system area is specified in a devicexx operand, Datareplicator automatically creates it and links it to the Datareplicator file system. You must ensure that the name of the file corresponding to an allocation file type has not already been allocated as a character special file.
You can specify the devicexx operand only in an individual definition section. If you specify it in the common definition section, Datareplicator detects an error during analysis of extraction definitions and cancels the subsequent processing. If the source HiRDB employs the single server configuration, specify the single server name as the server name at the start of the individual definition section (besdef).
The following is a definition example of the devicexx operand:
[Figure]

Note:
To omit a devicexx operand from the definition after Datareplicator has been operated using the devicexx operand:

Stop Datareplicator.
Delete the devicexx operand from the extraction environment definition.
Use the hdsfmkfs command to initialize the Datareplicator file system area that was specified with the deleted devicexx operand.
Execute initial start on Datareplicator.

If you delete a devicexx operand from the definition, and then execute initial start of Datareplicator without following the above procedure, an invalid file error might occur during execution.

5.3.3 Explanation of the operands