Explanation of the operands

sendhdsid=target-system-identifier
~ <hexadecimal> ((00-FF)) <<00>>
Specify the identifier of the data linkage target system. If the target system is the target Datareplicator, specify the target Datareplicator identifier. If the target system is XDM/DS, specify the target XDM/DS identifier in EBCDIK converted to hexadecimal.
hdeservice=service-name
~ <identifier of 1-64 characters> <<hirdbds>>
Specify the service name that was specified when the source Datareplicator's communication entry was added to the services file.

Example

This example target system consists of two server machines.

Provide a transmission environment definition for each server machine. For the service name, specify the service name that was specified when the source system's communication environment was configured. Make sure that the port number is the same as that of the target server machine.

The service name can be the same even if the target system's server machines have different target host names.

The following figure shows an example specification of a transmission environment definition when the target system consists of two server machines.
hdehost=target-host-name
~ <identifier of 1-255 characters> <<hdehost>>
Specify the host name that was specified when the target entry was added to the hosts file or DNS. Specify the host name as a string containing only alphanumeric characters, the dash (-), underline (_), and period (.) and beginning with an alphabetic character.
protocol=tcp|osi
Specify the protocol to be used for communications with the target system.

tcp

Use the TCP/IP protocol for communications.

osi

Use the OSI protocol for communications. If you specified sendmst in the sendcontrol operand in the extraction system definition, you cannot use the OSI communications protocol.

This operand is applicable only to the HP-UX edition of Datareplicator (excluding the IPF version).
extract_tselector=T-selector
~ <even number of hexadecimal digits with a length of 2-64 digits> <<00>>
Specify the same T-selector as for the target Datareplicator's reception process at the destination. Specify this operand if you use the OSI protocol for communication. Note that this operand is applicable only to the HP-UX edition of Datareplicator (excluding the IPF version).
nsap_address=NSAP-address
~ <even number of hexadecimal digits with a length of 2-40 digits> <<00>>
Specify the NSAP address of the machine where the target Datareplicator is running at the destination. Specify this operand if you use the OSI protocol for communication. Note that this operand is applicable only to the HP-UX edition of Datareplicator (excluding the IPF version).
senduoc=use|nouse
Specify whether a transmission data UOC routine is to be used.

use

Use a transmission data UOC routine. If in the case of UNIX Datareplicator, there is no libsenduoc.sl under SHLIB_PATH, Datareplicator assumes nouse. If, in the case of Windows Datareplicator, there is no senduoc.dll under PATH, a DLL loading error occurs and transmission stops.

nouse

Do not use a transmission data UOC routine.
sendintvl=transmission-interval
~ <unsigned integer> ((0-1440)) <<5>>
Specify the transmission interval to be used for sending extracted update information to the target system. You use thesendintvl_scale operand to specify the units of the transmission interval. If you specify 0, Datareplicator sends the update information in units of transactions. If you want to reduce the time leading up to import processing, start tuning from one second. Specifying 0 might slow down the transmission processing.

When applying data linkage to tables for which the WITHOUT ROLLBACK option is specified:

For tables for which the WITHOUT ROLLBACK option is specified, one update operation is treated as one transaction. If 0 is specified in this operand, transmission processing occurs each time a table for which the WITHOUT ROLLBACK option is specified is updated, resulting in a large amount of transmission processing overhead. If you apply data linkage to tables for which the WITHOUT ROLLBACK option is specified, we recommend that you specify a nonzero value in this operand.

sendintvl_scale=minute|second
Specify the units of the sendintvl operand value.

minute: Assume that the value of the sendintvl operand is in minutes.

second: Assume that the value of the sendintvl operand is in seconds.

This operand is applicable only when the sendintvl operand is specified. To specify this operand in an individual definition section, you must specify the sendintvl operand again in the same besdef. If you omit the sendintvl operand, Datareplicator ignores the sendintvl_scale operand.
The following table shows the combinations of sendintvl and sendintvl_scale operands and their relationship with a valid value:

Specification in an individual definition section		Specification in the common definition section
		sendintvl specified		sendintvl omitted (sendintvl_scale is ignored)
		sendintvl_scale specified	sendintvl_scale omitted	sendintvl omitted (sendintvl_scale is ignored)
One sendintvl specified	sendintvl_scale specified	Interval: Value specified in the individual definition section is effective. Units: Value specified in the individual definition section is effective.	Interval: Value specified in the individual definition section is effective. Units: Value specified in the individual definition section is effective.	Interval: Value specified in the individual definition section is effect. Units: Value specified in the individual definition section is effective.
One sendintvl specified	sendintvl_scale omitted	Interval: Value specified in the individual definition section is effective. Units: Minutes is assumed.	Interval: Value specified in the individual definition section is effective. Units: Minutes is assumed.	Interval: Value specified in the individual definition section is effective. Units: Minutes is assumed.
sendintvl omitted (sendintvl_scale is ignored)		Interval: Value specified in the common definition section is effective. Unit: Value specified in the common definition section is effective.	Interval: Value specified in the common definition section is effective. Unit: Minutes is assumed.	Interval: 5 is assumed. Unit: Minutes is assumed.

nsndid001=transmission-suppressed-original-receiver-identifier [... [ nsndid256=transmission-suppressed-original-receiver-identifier ]]
~ <hexadecimal> ((00-FF))
Specify the identifiers of original receivers that are to be subject to suppression of update information transmission. You use this operand to prevent loopback in a data linkage system that consists of multiple systems, each of which has both a source and a target of transmission.
Specify in each transmission-suppressed-original-receiver-identifier the source Datareplicator identifier at a system that originally receives update information that was received by a target Datareplicator running under this source HiRDB (the source system that sent update information to this target system). For details about suppression of loopback, see 4.5 Designing the data linkage system mode.
You must specify the nsndid001 to nsndid256 operands consecutively in ascending order beginning with nsndid001. If they are not consecutive or in ascending order, Datareplicator uses only those identifiers that are specified consecutively in ascending order from the beginning. If the nsndid operand is omitted, Datareplicator sends all intended update information to the target system specified in the sendhdsid operand.
keepalive=true|false
Specify whether the keepalive option can be specified for the socket.

true

Specify the keepalive option.

false

Do not specify the keepalive option.
retrynum=connection-retries-count
~ <unsigned integer> ((0-256)) <<0>>
Specify the number of times communication establishment with the target system can be retried for transmission processing if it fails. Datareplicator attempts to reestablish communication with the target system up to the specified number of times. If 0 is specified, Datareplicator retries until connection is established successfully or a stop request is accepted.
The reconnection interval depends on the sendcontrol operand value. The following table shows the reconnection interval:

sendcontrol operand value Reconnection interval

nodemst Connection retry interval (retry_interval operand value)

sendmst Transmission interval (smt_sendintvl operand value)
retry_interval=connection-retry-interval
~ <unsigned integer>((1-60))<<60>>(seconds)
Specify a connection retry interval if you want connection to be reestablished immediately in the event of a system switchover in the target system. This operand is applicable only when nodemst is specified in the sendcontrol operand.
The interval specified in this operand is also applied to retries in the event connection is lost because the import information queue file has become full. Note that when the import information queue file becomes full, a message reporting that the queue file is full is output at this retry interval, so the message might be output frequently if the specified value is too small.
overwrite=true|false
Specify whether transmission processing to the target system specified in sendhdsid is to be placed in the reduced mode when the extraction information file queue becomes full.
If you specified uap in the reflect_mode operand in the transmission environment definition, specify false. If you specify any other value in this operand in such a case, the KFRB00847-E message will be output.

true

Apply reduced-mode transmission processing to the target system. When the extraction information file queue becomes full, Datareplicator cancels the corresponding transmission processing and discards the update information subject to transmission from the extraction information queue file. In this case, the target system at the corresponding destination requires re-creation of the target database because conformity between the source and target databases is lost.

false

Do not apply the reduced-mode transmission processing to the target system.
overwrite_continue=true|false
Specify whether the reduced mode specified with the overwrite operand is to be inherited the next time transmission processing is restarted.

true

When transmission processing is restarted in the reduced mode, inherit the reduced mode by detecting a transmission process start error.

false

When transmission processing is restarted in the reduced mode, release the reduced mode and restart transmission processing from the transaction that was extracted after the restart.
maxtran=maximum-concurrently-executable-transactions-count
~ <unsigned integer> ((5-17800000)) <<100>>
Specify the number of transactions that can be executed concurrently to determine the initial value of the transaction management information buffer that will be used to edit and send update information. The initial value of the transaction management information buffer is obtained internally as the product of the maximum number of concurrently executable transactions specified with the maxtran operand and the maximum number of update information items per transaction specified with the maxtrandata operand. Specify the maxtran and maxtrandata operands so that their product does not exceed 89000000. For details about the size of the transaction management information buffer, see 4.6.4 Designing the transmission procedure.
maxtrandata=maximum-update-information-items-per-transaction
~ <unsigned integer> ((5-17800000)) <<500>>
Specify the maximum number of update information items that can be handled in a single transaction to determine the initial value of the transaction management information buffer that will be used to edit and send update information. If you have specified the ukey clause in the extract statement in the extraction definition, double the value to take into account the number of update information items for which pre-update data is stored.
The initial value of the transaction management information buffer is obtained internally as the product of the maximum number of concurrently executable transactions specified with the maxtran operand and the maximum number of update information items per transaction specified with the maxtrandata operand. Specify the maxtran and maxtrandata operands so that their product does not exceed 89000000. For details about the size of the transaction management information buffer, see 4.6.4 Designing the transmission procedure.
readbufnum=extraction-information-queue-I/O-buffers-count-for-transmission
~ <unsigned integer> ((1-255)) <<1>>
Specify the number of extraction information queue I/O buffers for transmission that are to be used to read update information from the extraction information queue file when update information is to be transmitted. Use the quiosize operand in the extraction environment definition to specify the size of the extraction information queue I/O buffers for transmission. For details about the extraction information queue I/O buffers for transmission, see 4.6.4 Designing the transmission procedure.
editbufsize=update-information-editing-buffer-size
~ <unsigned integer> ((1-2097151)) <<300>> (KB)
Specify the size of the update information editing buffer that is used to edit update information read from the extraction information queue file into the format supported by the target system. For details about the size of the update information editing buffer, see 4.6.4 Designing the transmission procedure.
You can reduce the number of communications by specifying a large value in this operand. We recommend that you specify a value that is greater than the amount of data (amount of update information) that is written to the extraction information queue file within the amount of time specified in the sendintvl operand.
To determine the amount of data that is written to the extraction information queue file, execute periodically the hdestate command and measure the amount of increase in the offset information indicated by the Queue write position.

sendcontrol operand value	Reconnection interval
nodemst	Connection retry interval (retry_interval operand value)
sendmst	Transmission interval (smt_sendintvl operand value)

prg_eventno=event-number
~ <unsigned integer> ((0-255))
Specify the number of the event to be sent to the target system when the transmission process detects PURGE TABLE update information for a partitioned table spanning multiple back-end servers. The transmission process's action depends on the event number that you specify here. The following table shows the event numbers and the corresponding transmission process actions:

Specified event number	Transmission process's action
Not specified	Ignores the corresponding PURGE TABLE and continues transmission processing.
0	Sends a normal termination log to the target system, and then terminates transmission processing (transmission process stops).
Other	Sends the event corresponding to the number specified in the prg_eventno operand to the target system, and then resumes transmission processing.

int_trc_getv=true|false
Specify whether activity trace information is to be collected for transmission processes on this node (applicable to the commondef common definition section) or this back-end server (applicable to a besdef individual definition section).

true

Collect activity trace for each transmission process.

false

Do not collect activity trace for each transmission 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.
queue_read_wait_interval=transmission-process's-extraction-information-queue-file-read-interval
~ <unsigned integer> ((100-60000)) <<2000>> (milliseconds)
Specify the interval after which the next read operation is to be restarted once the end of the extraction information queue file is detected under the control of the transmission process.
By specifying a small value in this operand, you can improve the spontaneity of transmission processing because of the brief wait time after the end of the extraction information queue file is detected. However, this might have an adverse effect on performance because the CPU utilization factor increases. You must take into account the frequency of update processing and CPU performance in specifying this value.
recvwatchtime = data-reception-line-monitoring-interval
~ <unsigned integer> ((1-35791394)) <<10>> (minutes)
Specify the line monitoring interval between extraction and import. If there is no response within the time specified in this operand, Datareplicator closes the line and retries connection establishment.
A smaller value detects line errors at an early stage. However, if the value is too small, unnecessary line disconnects and reconnects occur in cases such as the following. If this happens, you will need to adjust the operand value:
- The target system's workload is high and it takes time to store the transmitted data in the import information queue files.
- There is a high editbufsize operand value in the transmission environment definition and the amount of data to be written into the import information queue file at one time is large.
- The workload of the communication line is high and it takes time to respond from the target.
send_delay_limit_time=transmission-delay-period-threshold
~ <unsigned integer> ((0-86400)) <<0>> (seconds)
Specify the threshold value for the difference (transmission delay period) between the time at which update information is stored in the system log file and the time at which update data is sent and the target DBMS completes its reception. If the transmission delay period is greater than the threshold value specified here, a warning message is output.
You must also take into account the values of the queue_read_wait_interval and sendintvl operands in the transmission environment definition. If you specify a value of 0, the delay monitoring facility is disabled for transmission 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 15 minutes (900 seconds).

Example

The following figure shows an example of operation when the start of transmission processing is delayed.

Figure 5-6 Example of operation when the start of termination processing is delayed

This example executes only extraction processing from 8:00 to 17:00 and starts transmission processing after 17:00. To monitor the transmission delay period in such an operating environment, you must take into account that update data is not transmitted for up to 9 hours, during which period it is accumulated at the target system. Therefore, a period of 9 hours must be added to the threshold for the transmission delay period.
reflect_mode= server|uap
Specify whether the import transaction synchronization facility is to be used at the target Datareplicator.

server

Do not use the import transaction synchronization facility.

uap

Use the import transaction synchronization facility.

When you specify uap in this operand, you must specify the eventsync operand; you must also specify false in the overwrite operand.
eventsync=synchronous-event-code
~ <unsigned integer> ((1-128))
Specify the event code for a synchronous event.
To specify this operand, you must specify uap in the reflect_mode operand.
Specify in this operand a value that is different from event codes specified in the eventcntreset and prg_eventno operands. An error will result if a duplicate value is specified.
eventcntreset=data-transmission-count-reset-event-code
~ <unsigned integer> ((1-128))
Specify the event code for resetting the data-transmission count. To synchronize resetting at the source and target Datareplicators, this value must be the same as the eventcntreset operand value in the import environment definition.

5.4.3 Explanation of the operands