This section explains the preparation of the following files, which are needed to use the source Datareplicator:

Files the user must create	Files created by the source Datareplicator during initial startup
Extraction system definition file Extraction environment definition file Transmission environment definition files Extraction definition file Duplexing definition file	Extraction definition preprocessing file Extraction information queue files Extraction master status file Extraction server status file Extraction master error information files Extraction node master error information files Extraction master trace file Extraction node master trace files Data linkage file Command log files Duplexing control file

For details about the files, see 3.2.2 Files and processes used during extraction processing.

For details about the handling of the files, see 6.4.2 Handling of the files used with the source Datareplicator.

The following table provides information about creating the files used with the source Datareplicator.

Table 4-32 Creating the files used with the source Datareplicator

Filename		File type#7		Number of files	Required/optional
		R#8	C#9
Definition files	Extraction system definition file#1	Y	N	1 per source system (1 per MGR if the source HiRDB is a parallel server#10)	Required
	Extraction environment definition file#1	Y	N	1 per source system (1 per MGR if the source HiRDB is a parallel server#11)	Required
	Transmission environment definition file#1	Y	N	1 per target identifier (1 per MGR for each target identifier if the source HiRDB is a parallel server#11)	Required
	Extraction definition file#2	Y	N	1 per source system (1 per MGR if the source HiRDB is a parallel server)	Required
	Duplexing definition file#1	Y	N	1 per source system (1 per MGR if the source HiRDB is a parallel server)	Optional
Extraction definition preprocessing file#3		Y	Y	1 per source system (1 per MGR if the source HiRDB is a parallel server)	Required
Extraction information queue files#4, #12		Y	Y	2 to 16 per source system (2 to 16 per BES if the source HiRDB is a parallel server)	Required
Status files#4, #12	Extraction master status file	Y	Y	1 per source system (1 per MGR if the source HiRDB is a parallel server)	Required
	Extraction server status file	Y	Y	1 per source system (1 per BES if the source HiRDB is a parallel server)	Required
Error information files#5, #6	Extraction master error information files	Y	N	2 per source system (2 per MGR if the source HiRDB is a parallel server)	Required
	Extraction node master error information files	Y	N	2 per source system (2 per server machine containing a BES if the source HiRDB is a parallel server)	Required
Activity trace files	Extraction master trace files	Y	N	2 per source system	Optional
	Extraction node master trace files	Y	N	2 per source system (2 per BES if the source HiRDB is a parallel server)	Optional
Data linkage file#4, #12		Y	Y	1 per source system (1 per BES if the source HiRDB is a parallel server)	Required
Command log files#6		Y	N	2 per source system	Optional
Duplexing control file#5		Y	N	1 per source system	Optional

Legend:

MGR: System manager

BES: Back-end server (includes back-end servers that do not contain any databases subject to extraction processing)

R: UNIX regular file or Windows file

C: UNIX character special file

Y: Can be created.

N: Cannot be created.

#1

Use an OS editor to create this file before starting the source Datareplicator.

#2

Use an OS editor to create this file before executing the hdeprep command.

#3

To create this file, execute the hdeprep command after you have created the extraction definition file but before you start the source Datareplicator. The extraction definition preprossing file is created automatically when the hdeprep command is executed. If the file is a character special file for UNIX, create a symbolic link to the character special file before you execute the hdeprep command.

#4

Before you start the source Datareplicator, execute the hdestart -i command to initialize the source Datareplicator. These files are created automatically when the hdestart -i command is executed. If the files are character special files for UNIX, create a symbolic link to the character special files before you start the source Datareplicator.

#5

These files are created automatically when the source Datareplicator is initialized.

#6

These files are created automatically when the source Datareplicator is started.

#7

Use the same file type for all the following files:

• Extraction information queue files
• Extraction server status file
• Data linkage file

#8

If the user creates the file (definition file), grant the read privilege to source Datareplicator users. Grant the write privilege as appropriate. For a file that is not created by the user (definition file), do not change the privilege.

#9

An OS command is used to create character special files. If you use a character special file, set the following privileges:

Data linkage file:

Grant the read and write privileges to source Datareplicator users and groups.

File other than data linkage file:

Grant the read and write privileges to source Datareplicator users.

If you use the system switchover facility, create the files in the character special file format.

When you configure the environment, we recommend that you execute the hdestart -i command with init specified to check file capacity so that a shortage of file capacity will not occur while the source Datareplicator is running.

#10

If the source HiRDB is a parallel server and different settings are used in HiRDB's environment variables (such as PDDIR, PDCONFPATH, and SHLIB_PATH) for each server machine, you can also create operands for the environment variables separately for each server machine.

#11

If the source HiRDB is a parallel server, you can also create this file for each BES.

#12

In UNIX, if the file type is OS regular files, data might not be output in the event of a system failure. Because the source Datareplicator uses the extraction information queue file, extraction status file, and data linkage file during error recovery, a failure cannot be recovered if no data has been output to these files. We recommend that you use character special files that have high reliability for the extraction information queue file, extraction status file, and data linkage file.

The following table describes the settings for the files used at the source Datareplicator.

Table 4-33 File settings used at the source Datareplicator

File type	File name	Setting
Extraction system definition file	$HDEPATH/hdeenv	For the information to be defined, see 5.2 Extraction system definition.
Extraction environment definition file	any-directory/any-name	For the information to be defined, see 5.3 Extraction environment definition. Specify any-name in the extdef operand in the extraction system definition.
Transmission environment definition file	any-directory/any-name	For the information to be defined, see 5.4 Transmission environment definition. Specify any-name in the senddef01 through senddef64 operands in the extraction system definition.
Extraction definition file	any-directory/any-name	For the information to be defined, see 5.5 Extraction definition. Specify any-name when you execute the hdeprep command and create the extraction definition preprocessing file.
Duplexing definition file	any-directory/any-name	For the information to be defined, see 5.7 Duplexing definition (source). Specify any-name in the file_dupenv operand in the extraction system definition file.
Extraction definition preprocessing file	$HDEPATH/hde_prpfile	--
Extraction information queue file #	any-directory/any-name_server-name	Specify any-name in the qufile001 through qufile016 operands in the extraction environment definition. The specified name appended with _server-name becomes the file name. Make sure that the file name is unique in the source system. If the source HiRDB is a parallel server, make sure that the file name is unique on each back-end server. Specify the file size in the queuesize operand in the extraction environment definition.
Extraction master status file #	$HDEPATH/mststatus	--
Extraction server status file #	$HDEPATH/sts_server-name	--
Extraction master error information file	$HDEPATH/msterrfile1 $HDEPATH/msterrfile2	Specify the file size in the errfilesz operand in the extraction system definition.
Extraction node master error information file	$HDEPATH/errfile1 $HDEPATH/errfile2	If true is specified in the errfile_unique operand in the extraction system definition, errfile1_host-name and errfile2_host-name become the file names. Specify the file size in the errfilesz operand in the extraction system definition.
Extraction master trace file	$HDEPATH/msttrc.trc1 $HDEPATH/msttrc.trc2	Specify the file size in the int_trc_trcfilesz operand in the extraction system definition. The file can be edited and referenced by using the hdstrcedit command.
Extraction node master trace file	$HDEPATH/exttrc.trc1 $HDEPATH/exttrc.trc2	Specify the file size in the int_trc_trcfilesz operand in the extraction system definition. If true is specified in the errfile_unique operand in the extraction system definition, exttrc.trc1_host-name and exttrc.trc2_host-name become the file names. The file can be edited and referenced by using the hdstrcedit command.
Data linkage file#	$HDEPATH/hde_server-name	--
Command log file	any-directory/any-name_server-name	--
Duplexing control file	$HDEPATH/hde_fileenv.prp	--

Legend:

--: Not applicable

#

The file can be duplexed. However, if a file system area is used, the file cannot be duplexed.