HiRDB Dataextractor Version 8 Description, User's Guide and Operator's Guide

[Contents][Index][Back][Next]

Appendix B. Functional Differences with Windows

This appendix explains points that differ from the normal usage procedures when the OS being used is Windows.

Organization of this section
(1) Differences in available facilities
(2) Notes
(3) Environment setup procedure
(4) Startup and termination
(5) Specification differences with HiRDB Dataextractor
(6) Message output destinations

(1) Differences in available facilities

(a) OSI protocol

Only the TCP/IP protocol is supported; the OSI protocol is not supported.

(b) Import operation without creating an output file

You cannot import data into a table without creating an output file.

(2) Notes

(3) Environment setup procedure

(a) Directories and files created by HiRDB Dataextractor

Table B-1 lists the directories and files that are created by HiRDB Dataextractor during installation.

Table B-1 Directories and files created by HiRDB Dataextractor

Directory name and filename Description Type
Source Target
installation-directory Directory used to store various HiRDB Dataextractor directories and files Y Y
installation-directory\bin Directory used to store HiRDB Dataextractor's executable files (HiRDB Dataextractor's load modules and commands are stored in this directory) Y Y
installation-directory \bin\pxtmsvc.exe HiRDB Dataextractor's executable files Y Y
installation-directory \bin\pxtload.exe Y Y
installation-directory \bin\xtrep.exe Files for HiRDB Dataextractor's xtrep command Y Y
installation-directory \bin\xtmsgtext.dll Text files used to output HiRDB Dataextractor messages Y Y
installation-directory \conf\hirdbxtc.ini1 HiRDB Dataextractor's environment variable information setup file Y 2 (Y)
installation-directory \conf\hirdbxt.ini1 HiRDB Dataextractor's environment variable information setup file Y 3 Y
installation-directory \lib\maptable\euc2jis.map Mapping table for character code conversion (from EUC to SJIS) Y Y
installation-directory \lib\maptable\eucg2j.map Mapping table for character code conversion (from EUC to SJIS) Y Y
installation-directory \lib\maptable\euc2ucs2.map Mapping table for character code conversion (from EUC to UCS2) Y Y
installation-directory \lib\maptable\eucg2u.map Mapping table for character code conversion (from EUC to UCS2) Y Y
installation-directory \lib\maptable\jis2euc.map Mapping table for character code conversion (from SJIS to EUC) Y Y
installation-directory \lib\maptable\jis2ucs2.map Mapping table for character code conversion (from SJIS to UCS2) Y Y
installation-directory \lib\maptable\ucs22euc.map Mapping table for character code conversion (from UCS2 to EUC) Y Y
installation-directory \lib\maptable\ucs22jis.map Mapping table for character code conversion (from UCS2 to SJIS) Y Y
installation-directory\lib\usermap4 Directory containing the user's mapping tables for character code conversion -- Y
installation-directory \spool\5 Directory used to store files output during HiRDB Dataextractor operation Y Y

Y: Created.

(Y): Created but not used.

Source: Source system

Target: Target system

installation-directory: Directory in which HiRDB is installed

1 HiRDB Dataextractor creates the environment variable information setup files (hirdbxtc.ini and hirdbxt.ini) during installation. If you install a new version of HiRDB Dataextractor without uninstalling the previous version in the same directory, HiRDB Dataextractor creates environment variable information setup files with the names hirdbxtcXX.ini and hirdbxtXX.ini (where XX is 00 to 99). However, HiRDB Dataextractor uses hirdbxtc.ini and hirdbxt.ini.

2 This file is used only when extracted data is to be imported into a HiRDB.

3 This file is used only when XDM/XT is used to extract data from HiRDB and then import it into XDM/RD or create a sequential dataset.

4 This file is created when a mapping table is updated for the first time by the xtccnvedt command.

5 installation-directory\spool\ contains files that are created dynamically by HiRDB Dataextractor. You must not delete any of these files during HiRDB Dataextractor operation. Also, never delete installation-directory\spool\. The files created in installation-directory\spool\ during HiRDB Dataextractor operation are the same as those created when the UNIX operating system is used.

(b) Environment variables required in order to use HiRDB Dataextractor

HiRDB Dataextractor's environment variables are specified in the files listed below, which are created by HiRDB Dataextractor during installation. These files already contain environment variables; modify them as appropriate to your user environment. These files can be specified at the same time as the HiRDB.ini file, which specifies client environment variables; the values specified for these files have priority.

(i) Environment variables on data source system (for data extraction and import between HiRDBs)
The following is the procedure for specifying the hirdbxtc.ini file:
Format
[Figure]
[individual-environment-name] ~ <alphanumeric characters with no spaces > ((1-64 characters))
Notes
  • There is no restriction on the number of individual environment names that can be specified, but large files may use up memory and disable operation.
  • Each section requires at least one environment variable.
  • If the same section is specified more than once, the first section specified takes effect.
  • You must specify the brackets ([]) because they indicate the section name.

(ii) Environment variables on data source system (for XDM/XT linkage)
The following is the procedure for specifying the hirdbxt.ini file:
Format
[Figure]
[service-name] ~ <alphanumeric characters with no spaces > ((1-64 characters))
Notes
  • You can specify a maximum of 16 service name sections.
  • Each section requires at least one environment variable.
  • An error results if a service name is duplicated or more service names are specified than the permitted maximum.
  • You must specify the brackets ([]) because they indicate the section name.
(c) Environment variables to be specified

Table B-2 lists the environment variables that are required in order to use HiRDB Dataextractor. The environment variable names specified in the [HiRDB Dataextractor] section are used as the initial values for the environment variables specified in the other sections.

Some HiRDB versions allow HiRDB environment variables to be specified in HiRDB Dataextractor's environment variable information setup file.

Table B-2 Environment variables required in order to use HiRDB Dataextractor

Environment variable specification Source system Target system
HiRDB XDM/XT
File hirdbxtc.ini hirdbxt.ini hirdbxt.ini
Environment variables specifiable for HiRDB Dataextractor1 [XTHOST]
[XTPORTNO]
[XTLOGNAME]

[XTTMPDIR]
[XTLOGNAME]
[XTOPNWTIME]

[XTTMPDIR]
[XTLOGNAME]
[XTOPNWTIME]
Environment variables specifiable for HiRDB1 [PDUSER]2
[PDDIR]2
[PDCONFPATH]2
[PDUXPLDIR]2
[other-environment-variable]
PDUSER2
[PDDIR]2
[PDCONFPATH]2
[PDUXPLDIR]2
[other-environment-variable]
PDUSER2
[PDDIR]2
[PDCONFPATH]2
[PDUXPLDIR]2
All other environment variables are ignored.

HiRDB: Import of extracted data into a HiRDB

XDM/XT: Use of XDM/XT to extract data from HiRDB and then import it into XDM/RD or create a sequential dataset

1 Environment variables can be specified in each section.

2 This environment variable must be set when the HiRDB for data extraction or import uses a setup identifier.

(d) Environment variable specification format

Format
environment-variable-name=[environment-variable-value]

Note

If you omit an environment variable's value, HiRDB Dataextractor assumes that the specified environment variable is not to be set.

Rules
(e) Files required in order to use HiRDB Dataextractor

Table B-3 lists the files that are required in order to use HiRDB Dataextractor and which differ from the files required when the UNIX operating system is used.

Table B-3 Files required in order to use HiRDB Dataextractor that differ from the files required when the UNIX operating system is used

Filename Description Type
Source system Target system
HiRDB XDM/XT
installation-directory\conf\ hirdbxtc.ini Contains the environment variables used for data extraction in order to extract and import data between HiRDBs. Y -- --
installation-directory\conf\ hirdbxt.ini Contains the environment variables used to import data into HiRDB and to import extracted data into XDM/XT. -- Y Y
hosts file1 Contains the target host name at the target system. Y -- --
services file2 Contains the service name and port number for HiRDB Dataextractor. -- Y Y

Y: Required.

--: Not required.

installation-directory: Directory in which HiRDB Dataextractor is installed

HiRDB: Import of extracted data into HiRDB

XDM/XT: Use of XDM/XT to extract data from HiRDB and then import it into XDM/RD or create a sequential dataset

1 Windows-system-directory\system32\drivers\etc\hosts

2 Windows-system-directory\system32\drivers\etc\services

(4) Startup and termination

The following explains the procedures for operating and handling HiRDB Dataextractor that differ from when the UNIX operating system is used.

(a) Starting HiRDB Dataextractor

Start HiRDB Dataextractor at the following hosts:

The following explains the HiRDB Dataextractor startup procedures for automatic startup and manual startup.

After you set up the services file, Hitachi recommends that you set up HiRDB Dataextractor for automatic startup.

Automatic startup

This procedure starts HiRDB Dataextractor automatically when Windows is started. For automatic startup of HiRDB Dataextractor, you must use the Windows service.

  1. On the Administrative Tools page, double-click the Service icon.
  2. On the Service page, double-click the HiRDB Dataextractor service in the list box.
  3. For Startup Type, select Automatic.

Manual startup

You use this procedure to start HiRDB Dataextractor manually. In this case, HiRDB Dataextractor is started from the Windows service.

  1. On the Administrative Tools page, double-click the Service icon.
  2. On the Service page, select HiRDB Dataextractor from the list box.
  3. Choose the Start button to start HiRDB Dataextractor.
(b) Terminating HiRDB Dataextractor

The following explains the procedure for terminating HiRDB Dataextractor. The Windows service is used to terminate HiRDB Dataextractor.

Termination from the Windows service
  1. On the Administrative Tools page, double-click the Service icon.
  2. On the Service page, select HiRDB Dataextractor from the list box.
  3. Choose the Stop button.

(5) Specification differences with HiRDB Dataextractor

(a) xtrep command

The following explains the xtrep command specifications that are different from when the UNIX operating system is used.

xtrep
                 :
                 :
      {-o [output-filename]|-O[output-filename]}
      [-a individual-environment-section-name]
                 :
                 :

Y: Specified.

N: Not specified.

specified-output-filename: Output filename specified in the -o or -O option

%XTTMPDIR%: Value specified in the XTTMPDIR environment variable

Note
Any spaces or commas in a specified output filename or extraction table name are converted to the underscore character (_) in the created filename.
(b) Notes on command specification

(6) Message output destinations

Table B-5 shows the message output destinations.

Table B-5 Message output destinations

Output destination Source system Target system
HiRDB XDM/XT
Error log file (installation-directory\spool\xter) Y1 Y2 Y2
Standard output Y -- --
Event log Y Y Y

Y: Output.

--: Not output.

HiRDB: Import of extracted data to HiRDB

XDM/XT: Use of XDM/XT to extract data from HiRDB and then import it into XDM/RD or create a sequential dataset

1 If the XTLOGNAME environment variable is omitted, HiRDB Dataextractor assigns a unique filename. You can output messages to a desired file by specifying the -e option in the xtrep command. In such a case, the specified filename takes precedence over the value set in the XTLOGNAME environment variable. If an error occurs during parameter analysis, this file is not created, and HiRDB Dataextractor outputs error messages to the standard output only.

2 If the XTLOGNAME environment variable is omitted, HiRDB Dataextractor assigns a unique filename.