HiRDB Dataextractor enables the user to specify desired information in the following SQL statements that are issued when data is extracted from an ORACLE database.

• LOCK TABLE statement
• SELECT statement

Table 5-2 explains the scope of this function.

Table 5-2 Scope of the SQL user specification function during ORACLE data extraction

Data linkage type	Source	Target	Applicability
XDM/XT linkage	XDM/RD	HiRDB	--
		Sequential dataset	--
	ORACLE	XDM/RD	Y
		Sequential dataset	Y
HiRDB Dataextractor linkage	ORACLE	HiRDB	Y
		Binary-format file	Y
		DAT-format file	Y

Y: Applicable

--: Not applicable to HiRDB Dataextractor

(a) Use with XDM/XT linkage

To use this function when data is extracted from an ORACLE database with XDM/XT linkage, the following specifications are required:

• XDM/XT's JXUMCTL control statement
  RDBDEF and EXTRACT statements
  
• HiRDB Dataextractor's environment variable information setup file (source system)

The following table lists the environment variables that must be specified in the environment variable information setup file:

Environment variable	Specification
PDHOST	As required*
PDNAMEPORT	As required*
XTEXTRACTDB	Mandatory
XTLCKxxxx	As required
XTTBLxxxx	As required
XTCLMxxxx	As required
XTWHExxxx	As required

Mandatory: Specification is mandatory.

As required: Specify as appropriate.

^* This environment variable is required when the RDBDEF statement is specified in XDM/XT's JXUMCTL control statement.

For details about the environment variables, see 2.2.3 Specifying environment variables.

(b) Use with HiRDB Dataextractor linkage

To use this function when data is extracted from an ORACLE database with HiRDB Dataextractor linkage, you execute the xtrepO command.

Environment variable

The XTSQL environment variable must be specified in the source system.

Command options

The following table describes the options whose specification is related to this function:

Command	Option	Value	Import to HiRDB		Binary or DAT file creation
			XTSQL		XTSQL
			0	1	0	1
xtrepO	-g	--	O	M	O	M
		lock-information-file
	-r	[authorization-identifier,]table-identifier	O	M	N	N
	-R	--	N	N	M	M
		{bin|dat}
	-s	column-name-specification-file-name	O	O	O	O
	-w	table-expression-specification-file-name	O	N	O	N
	[authorization-identifier,]table-identifier	--	M	N	M	N
	table-expression-specification-file-name	--	N	M	N	M

M: Mandatory

O: Optional

N: Not specifiable

--: Not specified

• -g [lock-information-file-name]
  The combination of this option and the XTSQL environment variable is used to perform lock control on the table from which data is extracted. Specification of this option is mandatory when 1 is specified in the XTSQL environment variable.
  The following table provides the details of the lock information file specification:
  

  XTSQL	-g option		Action
  0	Omitted	--	Issue LOCK TABLE using the table name entered on the command line.
  	Specified	No value specified	Do not issue LOCK TABLE.
  		Value specified	Issue LOCK TABLE based on information in the lock information file.
  1	Omitted	--	Error
  	Specified	No value specified	Do not issue LOCK TABLE.
  		Value specified	Issue LOCK TABLE based on information in the lock information file.

• -r [authorization-identifier,]table-identifier
  This option or the -R option must be specified when 1 is specified in the XTSQL environment variable.
  
• -R [{bin|dat}]
  This option or the -r option must be specified when 1 is specified in the XTSQL environment variable.
  
• -s column-name-specification-file-name
  If necessary, specify the absolute path of the column name specification file.
  
• -w table-expression-specification-file-name
  This option cannot be specified when 1 is specified in the XTSQL environment variable.
  
• [authorization-identifier,]table-identifier
  Specify this option when the XTSQL environment variable is omitted or 0 is specified in the XTSQL environment variable.
  
• table-expression-specification-file-name
  Specify this option when 1 is specified in the XTSQL environment variable.
  

For details about these options, see 5.1.2 xtrepO command.

File specification method

This subsection describes the specification of files in options.

• Lock information file
  This file specifies the lock options in the LOCK TABLE statement.
  Specify the file contents as follows, as appropriate to the specification of XTSQL:
  

  XTSQL	Specification
  0	Specify the lock options that follow LOCK TABLE table-name.
  1	Specify the lock options that follow LOCK TABLE.

• Table expression specification file
  This file specifies the table expression in the SELECT statement.
  Specify the file contents as follows, as appropriate to the specification of XTSQL:
  

  XTSQL	Specification
  0	Specify the table expression that follows FROM table-name in the SELECT statement.
  1	Specify the table expression that follows FROM in the SELECT statement.

Note

When 1 is specified in the XTSQL environment variable, no column name can be specified in the null value information file. If you specify information such as a default null value or data format of repetition columns, specify applicable field numbers. Specifying column names results in an error.

When data is imported into a HiRDB table, HiRDB Dataextractor starts HiRDB's database load utility (pdload). The loader parameter specification function enables you to specify desired parameters for pdload.

Table 5-3 explains the scope of this function.

Table 5-3 Scope of loader parameter specification function (when ORACLE data is extracted)

Data linkage type	Source	Target	Applicability
HiRDB Dataextractor linkage	ORACLE	HiRDB	Y

Y: Applicable

(a) Use

To use this function when data is extracted from an ORACLE database, execute the xtrepO command.

Environment variables

At the source system, specify the following environment variables as necessary:

• XTLPRMxxxx
• XTPDSRxxxx

Command options

The following table describes the options whose specification is related to this function:

Command	Option	Value	Requirement
xtrepO	-d	--	1'
	-f	server-name	O
	-i	{c|s|n|x}	1'
	-I	XTPDCFxxxx	O
		XTLPRMxxxx	M, 1
		XTPDSRxxxx	M, 2
	-j	RDAREA-name	O
	-l	{a|p|n}	1'
	-n	buffer-sectors-count	1'
	-q	error-data-file-name,count	2'
	-v	null-value-information-file	O
	-z	--	1'

M: One of these items is required in order to use this function.

O: This item is optional.

1, 1': These items are mutually exclusive

2, 2': These items are mutually exclusive

• -I [XTPDCFxxxx][,XTLPRMxxxx][,XTPDSRxxxx]
  Specify at least one value. You can specify multiple values in any order by using the comma (,) as the delimiter.
  

XTPDCFxxxx (name of pdload control information environment variable)

Specify this information as necessary. For details about the environment variables, see 2.2.3 Specifying environment variables.

XTLPRMxxxx (name of pdload command line information environment variable)

To use this function, ensure that either the XTLPRMxxxx or the XTPDSRxxxx environment variable is specified.

Notes

• When you specify this environment variable, none of the following options can be specified:
  -d option
  -i option
  -l option
  -n option
  -z option
  
• When the name of this environment variable is specified, HiRDB Dataextractor does not specify any parameter other than the table name, control information file name, -b, -k, or -v option when pdload starts; therefore, specify all necessary options in the pdload command line information file.

XTPDSRxxxx (name of pdload control information file's source statement information environment variable)

To use this function, ensure that either the XTLPRMxxxx or the XTPDSRxxxx environment variable is specified.

Note

When you specify this environment variable, do not specify the -q option, as it cannot be specified.

This function converts the character codes of the data extracted from the ORACLE database according to specified environment variables and then imports the data.

Table 5-4 explains the scope of this function.

Table 5-4 Scope of the character code conversion function (when ORACLE data is extracted)

Data linkage type	Source	Target	Applicability
HiRDB Dataextractor linkage	ORACLE	HiRDB	Y
		Binary-format file	Y
		DAT-format file	Y

Y: Applicable

(a) Using the character code conversion function

By specifying environment variables and a null value information file, you can convert the character codes during data import processing.

For details about the environment variables, see (3) Character code conversion function in 4.2.3 Additional data extraction and import functions. For details about the null value information file, see (5) Null value information file in 5.1.4 Contents of files specified with the xtrepO command.

For details about converting Gaiji codes, see (3) Character code conversion function in 4.2.3 Additional data extraction and import functions.