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

Figure 2-6 Target Datareplicator's directory structure (Windows)

#

Environment variable that indicates the directory that stores the Datareplicator definitions.

Table 2-16 Contents of directories and files created by a target Datareplicator (Windows)

Creation time	Directory and filename#1, #2	Description
Created by the user	%HDSPATH%\hdsenv	Import system definition file
	any-name	Import environment definition files
	any-name	Import definition files
	file-name-specified-in-file_dupenv-operand-in-extraction-system-definition-file	Duplexing definition file
Target Datareplicator's initial startup	any-name	Import information queue files
	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-name	Unimported information files
	any-name#3	Command log files
Created by the user	any-name	Update information definition file#4
Transferred by the user	any-name	SAM file#5
During execution of the update information input command	update-information-input-command-execution-directory\unextfile_data-linkage-identifier	Unextracted data storage file#6

#1: Each directory is created under a local drive.

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

#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 the OS path - 1.

#4: 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.

#5: 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.

#6: 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.