Figure 2-3 shows a target Datareplicator's directory structure, and Table 2-7 lists the file contents.

Figure 2-3 Target Datareplicator's directory structure (UNIX)

#

Directory that stores the Datareplicator definitions that are created in the target system.

Table 2-7 Contents of directories and files created by a target Datareplicator (UNIX)

Creation time	Directory and filename#1	Description
Created by the user	$HDSPATH/hdsenv	Import system definition file
	any-directory/any-name	Import environment definition files
	any-directory/any-name	Import definition files
	any-directory/any-name	Duplexing definition file
While connected with the source system	$HDSPATH/rcvrfile_xx_yy#2	Recovery information file
Target	any-directory/any-name	Import information queue files
Target Datareplicator's initial startup	any-name	Import status files
	$HDSPATH/hdsinitstate	Import master status file
	$HDSPATH/errfile1 $HDSPATH/errfile2	Import error information files
	$HDSPATH/reftrc.trc1 $HDSPATH/reftrc.trc2	Import trace files
	any-directory/any-name	Unimported information files
	any-directory/any-name#3	Command log files
	$HDSPATH/hds_fileenv.prp	Duplexing control file
	any-directory/file-with-extension-.mf#4	Work file
Created by the user	any-directory/any-name	Update information definition file#5
Transferred by the user	any-directory/any-name	SAM file#6
During execution of the update information input command	update-information-input-command-execution-directory/unextfile_data-linkage-identifier	Unextracted data storage file#7

#1: The HDSPATH environment variable specifies the directory used to create the target Datareplicator's definitions.

#2: xx indicates the target Datareplicator identifier; yy indicates the data linkage identifier.

#3: Specify the absolute or relative path name of the command log file in the hds_command_log_file environment variable. If the relative path name is specified, the system assumes $HDSPATH/relative-path-name as the absolute path name. If you omit the hds_command_log_file environment variable, the system assumes $HDSPATH/hdscmdlog as the name of the command log file.

The actual command log file name has 1 or 2 appended at the end of the specified name. Make sure that the length of the actual command log file name does not exceed the maximum length of OS path - 1.

#4: This is a work file that is created automatically by Datareplicator when dual files are used. Do not delete this file while Datareplicator is running.

#5: Of mainframe databases when a SAM file is used, you must create an update information definition file for a target Datareplicator that extracts PDM2 E2 data. There is no need to create this file for any other Datareplicator.

#6: The update information extraction SAM file for the mainframe is sent by the file transfer program. You must create a SAM file when the target Datareplicator is linked to a mainframe database that uses SAM files (PDM2 E2 or RDB1 E2). There is no need to create this file for any other Datareplicator.

#7: The unextracted data storage file is created/re-created each time an update information input command is executed. Its filename is unextfile_ plus the data linkage identifier specified during execution of the update information input command.