Functional Differences with Solaris

LANG
If you omit the LANG environment variable, HiRDB Dataextractor assumes ja.
LD_LIBRARY_PATH
When you use the xtrep command to extract and import HiRDB data, specify the absolute path of the directory containing the extracting HiRDB's common library in the user environment where the xtrep command is entered. Use this environment variable instead of the existing SHLIB_PATH environment variable.

When XDM/XT is linked to extract data from HiRDB or to import data into HiRDB, the character code set specified in the LANG environment variable must be the same as the character type specified in the CONVERT XDM/XT control statement. If they are not the same, the results may not be correct.
If the null value information file is omitted, HiRDB Dataextractor assumes ## (SJIS codes X'81948194') as the default null value for the NCHAR and NVARCHAR attributes. If you omit the LANG environment variable or specify ja as its value, the data ## on the extracting HiRDB will not be stored as the null value by the importing HiRDB. To import ## data as the null value, specify ## in UJIS codes as a literal in the null value information file. For details about how to specify a null value information file, see 4.2.4 Contents of files specified with the xtrep command.
If you specify SPACE for a column with the NCHAR or NVARCHAR attribute in the null value information file, HiRDB Dataextractor uses a space (SJIS code X'8140') as the default null value. Therefore, if you omit the LANG environment variable or specify ja as its value, blank data on the extracting HiRDB will not be stored as the null value by the importing HiRDB. To import a space as the null value, specify the space in its UJIS code as a literal in the null value information file. For details about how to specify a null value information file, see 4.2.4 Contents of files specified with the xtrep command.

Appendix C. Functional Differences with Solaris