For details about how to handle the import system definition file, see 5.8.2 Modifying defined information.

For details about how to handle the import environment definition file, see 5.9.2 Modifying defined information.

For details about how to handle the import definition file, see 5.10.3 Modifying defined information.

The following explains how to handle the import information queue files.

Modifying a filename, the file size, or the number of files

When using a UNIX regular file or Windows file:

1. Terminate the source system.
2. Terminate the target Datareplicator normally.
3. Use a text editor to modify the corresponding operands in the import environment definition.
4. Execute initial start or partial initial start on the target Datareplicator.
5. Start the source system.

When using a UNIX character special file:

1. Terminate the source system.
2. Terminate the target Datareplicator normally.
3. Use an OS command to re-create the import information queue files in character special file format.
4. Use a text editor to modify the corresponding operands in the import environment definition as appropriate for the created import information queue files.
5. Execute initial start or partial initial start on the target Datareplicator.
6. Start the source system.

The following explains how to handle an import status file.

Changing the filename or file size

When using a UNIX regular file or Windows file:

1. Terminate the source system.
2. Terminate the target Datareplicator normally.
3. Use a text editor to modify the corresponding operands in the import environment definition.
4. Execute initial start or partial initial start on the target Datareplicator.
5. Start the source system.

When using a UNIX character special file:

1. Terminate the source system.
2. Terminate the target Datareplicator normally.
3. Use an OS command to delete the previous import status file.
4. Use an OS command to re-create the import status file in character special format.
5. Use a text editor to modify the corresponding operands in the import environment definition as appropriate for the created import status file.
6. Execute initial start on the source Datareplicator.
7. Start the source system.

The following explains how to handle the import master status file.

The import master status file is used to store execution results during initial start. It is created automatically when Datareplicator starts.

The following explains how to handle the import error information files.

(a) Changing the maximum size

To change the maximum size of the import error information files:

1. Terminate the source system.
2. Terminate the target Datareplicator.
3. Use a text editor to modify the appropriate operand in the import system definition.
4. Execute normal start on the target Datareplicator.
5. Start the source system.

(b) Saving an import error information file

When an import error information file subject to data accumulation becomes full, file swapping occurs. Datareplicator re-creates the next import error information file so that it can be swapped in.

To save the contents of an import error information file before it is re-created:

1. Use an OS command to check the most recent update dates and times of the import error information files.
2. Use an OS command to copy the import error information file with the older update date and time into a new file under any name. Datareplicator issues a message (KFRB00051-I or KFRB00052-I) whenever import error information files are to be swapped or whenever an import error information file is to be closed during Datareplicator operation; when this message is issued, make a backup copy if necessary.

(c) Outputting import error information to the standard output

When the import error information file being used for data accumulation becomes full, file swapping occurs. Datareplicator re-creates the next import error information file that is to be swapped in.

To output the contents of the import error information file to the standard output before the file is re-created:

1. Use an OS command to check the most recent update dates and times of the import error information files.
2. Use an OS command to output the import error information file with the older update date and time to the standard output.

(d) Example of import error information file output

The following figure shows an example of the output from an import error information file.

Figure 6-21 Example of the output from an import error information file

Explanation:

1. Fri ... 2002, process ..., function ...
   Fri ... 2002: Day of week, month, date, time (hh:mm:ss), and year when error occurred
   process: Name and number of internal process resulting in the error
   function: Name of internal function resulting in the error
   
2. errorcode: Error code of the error
3. information: Detailed information about the error

(e) Output destinations other than files

Datareplicator outputs information to the import error information files so that it can be used in the event of errors or to achieve automatic operation.

In the case of UNIX Datareplicator, this information is also output to the syslog file. To output information to the syslog file, you must specify true in the syslogout operand in the import system definition. The following table shows the output destinations for the contents of an import error information file.

Table 6-13 Output destinations of the contents of an import error information file

Status of the import error information file	Output destination
N/A	syslog file	Import error information file
Normal (output enabled)	If true	Y
Error (output disabled)	If true	--

Y: Output.

If true: Output if true is specified in the syslogout operand in the import system definition.

--: Not output.

You can use the hdstrcedit command to view and edit activity trace files (import trace files). For details about how to use the hdstrcedit command, see the hdstrcedit command in Chapter 7. Command Syntax.

The following explains how to handle an unimported information file.

(a) Changing the maximum size

To change the maximum size of an unimported information file:

1. Terminate the source system.
2. Terminate the target Datareplicator.
3. Use a text editor to modify the corresponding operand in the import environment definition.
4. Execute initial start or partial initial start on the target Datareplicator.
5. Start the source system.

(b) Saving the unimported information file

When an unimported information file being used for data accumulation becomes full, file swapping occurs. Datareplicator re-creates the next unimported information file that is to be swapped in.

To save the contents of an unimported information file before the file is re-created:

1. Use an OS command to check the most recent update dates and times of the unimported information files.
2. Use an OS command to copy the unimported information file with the older update date and time into a new file under any name.

(c) Sending the unimported update information to the standard output

The unimported information file that is subject to accumulation of information is swapped when it become full. A new unimported information file is re-created when this swapping occurs. If you want to send the contents of the unimported information file to the standard output before the file is re-created, follow the procedure below:

1. Use the OS command to check the update dates and times of the unimported information files.
2. Send the unimported information file that has the older update date and time to the standard output.

(d) Example of unimported information file output

The following figure shows an example of the output from an unimported information file.

Figure 6-22 Example of output from an unimported information file

Notes on the output format

• If a column's attribute is an abstract data type, Datareplicator uses a constructor function to import its data, and the update information value is output in the following format:
  

  column-name=FUNC(update-information-value)

  FUNC: Name of the constructor function
  
• If a column's attribute is repetition column and the update information indicates column-specified update processing, Datareplicator uses ARRAY to provide readable information in the following format (although actual update processing uses an iteration structure instead of ARRAY):
  

  column-name=ARRAY[update-information-value,update-information-value, ...,update-information-value]

• If a column's attribute is repetition column and the update information indicates element-specified update processing, Datareplicator outputs the information in the following format:
  

  column-name[element-number]=update-information-value

• If BLOB concatenation operation data is updated, Datareplicator outputs the information in the following format:
  

  column-name=column-name||*BLOB(data-length-in-bytes)*

• If BINARY concatenation operation data is updated, Datareplicator outputs the information in the following format:
  

  column-name=column-name||*BINARY(data-length-in-bytes)*

The following explains how to handle a command log file.

The command log files contain a record of when Datareplicator commands were executed. The command log files are created automatically when Datareplicator starts. You can view a command log file at any time to check the execution history of commands. For details about the information that is output to the command log file, see Overview of commands in 7. Command Syntax.

The following figure shows an example of the contents of a command log file.

Figure 6-23 Example of command log file contents

The following explains how to handle the update information definition file.

Modifying defined information

You can modify defined information before executing the hdssamqin command regardless of the target Datareplicator's status.

To modify defined information:

1. Use a text editor to modify the defined information.
2. Execute the hdssamqin command.

If the previous command has not terminated normally, do not modify the defined information. If you have modified defined information in such a case, execute the hdssamqin command with the -c option specified.

Transfer a SAM file created at a mainframe system that uses SAM files to the target Datareplicator or to a system that supports the update information input command (hdssamqin).

The following explains how to handle an unextracted data storage file.

(a) Checking the unextracted data storage file

If data has been stored in an unextracted data storage file, Datareplicator issues a message to that effect when execution of the hdssamqin command finishes. When this message is output, check the contents of the file.

(b) Saving the unextracted data storage file

An unextracted data storage file is created each time the hdssamqin command is executed. To save the file contents, use an OS command to save the contents under a different filename before executing the next hdssamqin command.

(c) Example of unextracted data storage file output

The following figure shows an example of the output from an unextracted data storage file.

Figure 6-24 Example of output from an unextracted data storage file