Neoview Character Sets Administrator's Guide (R2.4, R2.5)

• JMS URL
• Startseq
• endseq
• Comments
• Named control file elements including type format, data format, map, source, and job
When the Transporter client operates in pass-through mode, incoming data is recognized and
managed as single-byte containers, not as distinct and separate characters. Consequently, field
delimiters, nullstring, startseq, and endseq values should always be limited to single-byte
characters that will not be mistaken for the second byte of multibyte character data. Valid values
are the first 64 characters of the ASCII character set, including the 31 control characters, the
numbers 0 through 9, and the 21 punctuation mark characters that end with the question mark.
For more information about control file organization and syntax, see the Neoview Transporter
User Guide.
Encoding Transporter Client Event and Log File Messages
Event messages that are generated by the Transporter client and sent to the Neoview platform
are always encoded in UTF8.
Messages written to the log file are logged, by default, in the user's default encoding. Any character
that cannot be mapped is replaced, by default, with a question mark.
You can configure the encoding of the log file by editing the log4j.properties file located
in the $NVTHOME/conf directory. For example, adding this line to the file makes the log file
encoding UTF8:
log4j.appender.A1.encoding=UTF-8
It is useful to set the log file encoding to UTF8 when you are working with several different data
file encodings and the default client encoding is not UTF8. Using UTF8 prevents any characters
from being replaced by question marks.
If you change the encoding of the log file and the log file already exists, you should remove or
rename the file because log files that contain more than one encoding might not display correctly.
Messages that are written to the console that runs the Transporter client are always encoded in
the default character set of that machine. Characters that cannot be mapped are replaced, by
default, with question marks. Every message displayed on the Transporter client console is also
present in the log file.
How Character Encoding Is Implemented in the Neoview Loader
• Because the Neoview Loader does not perform character set translation (with its pass-through
flag is always set to ON), the character data in any input file for the Neoview Loader must
use the same encoding as is required for database encoding.
• You must enable the loader's pass-through mode flag to load UTF8 files into ISO88591
columns.
Table C-2 (page 52) provides guidelines for setting the value for the cSetConversion (-cc)
argument from gcmd for each of the Neoview character set configurations. A value of Y specifies
character set conversion. A value of N specifies no character set conversion.
Table C-2 Setting the Conversion of Input Data for the Neoview Loader
Unicode ConfigurationSJIS ConfigurationISO88591 Configuration
• Set the value of cSetConversion to
N for UTF8-encoded input data sent
to UCS2 columns.
• Set the value of cSetConversion to
Y for UTF8-encoded input data sent
to ISO88591 columns.
Set the value of cSetConversion to N
for SJIS-encoded input data.
Set the value of cSetConversion to N
for input data received when the
ISO88591 configuration is used.
52 Configuring Neoview Client Applications