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

Files the user must create	Files created by the target Datareplicator during initial startup
Import system definition file Import environment definition files Import definition files Duplexing definition file	Import information queue files Import status files Import master status file Import error information files Activity trace files Import trace files Unimported information files Command log files Duplexing control file

When the source database uses SAM files (PDM2 E2 or RDB1 E2), the user must also prepare the following files, in addition to the files listed above:

• Update information definition file
• SAM file
• Unextracted data storage file

For details about the files, see 3.3.2 Files and processes used during import processing.

For details about the handling of the files, see 6.7.2 Handling of the files used with the target Datareplicator.

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

Table 4-40 Creating the files used with the target Datareplicator

File name		File type#8		Number of files	Required/optional
		R#9	C#10
Definition files	Import system definition file#1	Y	N	1 per target system	Required
	Import environment definition file#1	Y	N	1 per data linkage identifier	Required
	Import definition#1	Y	N	1 per data linkage identifier	Optional#11
	Update information definition file#2	Y	N	1 per update information input command execution	Optional#12
	Duplexing definition file#1	Y	N	1 per target system (1 per MGR if the source HiRDB is a parallel server)	Optional
Import information queue file#3, #13		Y	Y	2 to 8 per data linkage identifier	Required
Status files	Import status file#3, #13	Y	Y	1 per data linkage identifier	Required
	Import master status file#3, #13	Y	Y	1 per target system	Required
Unimported information file#4, #5		Y	N	2 per data linkage identifier	Required
Import error information file#4, #5		Y	N	2 per target system	Required
Activity trace file (Import trace file)		Y	N	2 per target system	Optional
Command log file#5		Y	N	2 per target system	Optional
SAM file#6		Y	N	1 per update information input command execution	Optional#12
Unextracted data storage file#7		Y	N	1 per data linkage identifier	Optional#12
Duplexing control file#4		Y	N	1 per target system	Optional

Legend:

MGR: System manager

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 target Datareplicator.

#2

Use an OS editor to create this file before starting update information input processing (by executing the hdssamqin command) and import processing.

#3

Before you start the target Datareplicator, execute the hdsstart -i command to initialize the target Datareplicator. These files are created when the hdsstart -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 target Datareplicator.

#4

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

#5

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

#6

The SAM file created by the system containing the mainframe database that uses SAM files is transferred to the target Datareplicator by using the mainframe's file transfer program.

#7

When the hdssamqin command is executed, the file is created or re-created. If the file already exists, it is re-created with a size of zero bytes.

#8

Use the same file type for all the following files:

• Import information queue files
• Import status file

#9

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.

#10

An OS command is used to create character special files. If you use a character special file, grant the read and write privileges to target Datareplicator users. If you use the system switchover facility, create the files in the character special file format.

If you have created the import information queue file and import status file as character special files, execute initial start on the target Datareplicator by using the hdsstart -i -f command.

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

#11

This file can be omitted if the source and target tables have an identical format including the table name and column names.

#12

When SAM files are used for data linkage, this file is used to execute the update information input command (hdssamqin). In the case of RDB1 E2, the update information definition file is not needed.

#13

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 import information queue file, import status file, and import master status 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 these files.

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

Table 4-41 File settings used at the target Datareplicator

File type	File name	Remarks
Import system definition file	$HDSPATH/hdsenv	For the information to be defined, see 5.8 Import system definition.
Import environment definition file	$HDSPATH/any-name	For the information to be defined, see 5.9 Import environment definition. Specify any-name in the refenv001 through refenv128 operands in the import system definition.
Import definition file	$HDSPATH/any-name	For the information to be defined, see 5.10 Import definition. Specify any-name in the reffile operand in the import environment definition.
Update information definition file	any-directory/any-name	For the information to be defined, see 5.11 Update information definition. Specify any-name when you execute the hdssamqin -n command.
Duplexing definition file	any-directory/any-name	For the information to be defined, see 5.12 Duplexing definition (target). Specify any-name in the file_dupenv operand in the import system definition file.
Import information queue file #	any-directory/any-name	Specify any-name in the qufile001 through qufile008 operands in the import environment definition. Specify the file size in the queuesize operand in the import environment definition.
Import status file#	any-directory/any-name	Specify any-name in the statsfile operand in the import environment definition. Specify the file size in the statssize operand in the import environment definition.
Import master status file #	$HDSPATH/hdsinitstate	--
Unimported information file	any-directory/any-name	Specify any-name in the unreffile1 and unreffile2 operand in the import environment definition Specify the file size in the unreffilesz operand in the import environment definition.
Import error information file	$HDSPATH/errfile1 $HDSPATH/errfile2	Specify the file size in the errfilesz operand in the import system definition.
Activity trace file (Import trace file)	$HDSPATH/reftrc.trc1 $HDSPATH/reftrc.trc2	Specify the file size in the int_trc_trcfilesz operand in the import system definition. The file can be edited and referenced by using the hdstrcedit command.
Command log file	any-directory/any-name	--
SAM file	any-directory/any-name	Specify any-name when you execute the hdssamqin -n command. 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.
Unextracted data storage file	any-directory/unextfile_data-linkage-identifier	--
Duplexing control file	$HDSPATH/hds_fileenv.prp	--

Legend:

--: Not applicable

#

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