HiRDB Dataextractor Version 8 Description, User's Guide and Operator's Guide
This section explains the format of messages issued by HiRDB Dataextractor. Table 8-1 lists the destinations of the HiRDB Dataextractor messages. For the destination of each message, see Table 8-1.
Table 8-1 Destinations of HiRDB Dataextractor messages
| Destination | Protocol | ||||
|---|---|---|---|---|---|
| TCP/IP | OSI | ||||
| Extraction 1 | Extraction 2 | Import/File creation | Extraction 2 | Import/File creation | |
| /opt/HIRDBXT/spool/xter | Y1 | Y2 | Y2 | N/A | N/A |
| /opt/HIRDBXT/spool/xtlog | N/A | N/A | N/A | Y2 | Y2 |
| Standard output | Y | N/A | N/A | N/A | N/A |
| Message log file3 | Y | Y | Y | Y | Y |
Y: Output.
N/A: Not output.
Extraction 1: Data extraction facility is executed with the xtrep command in order to extract and import data between HiRDBs.
Extraction 2: Data extraction facility is executed via a linkage with VOS3 XDM/XT.
Import/File creation: Data import facility or file creation facility is executed.
1 Specify a filename that is unique in HiRDB Dataextractor. You can output to a desired file by specifying the -e option in the xtrep command. This file is created when an error occurs during parameter analysis, in which case error messages are output to the standard output only.
2 Specify a filename that is unique in HiRDB Dataextractor.
3 When the OS being used is HP-UX, the message log file does not display national character data correctly. Consequently, if national character data is included in the embedded characters (such as a table identifier or column name) of a message text that is output to the message log file, that data is not displayed correctly. In such a case, check the contents of the error log file; the same message is also output to the error log file.
All rights reserved. Copyright (C) 2007, Hitachi, Ltd.