Neoview Character Sets Administrator's Guide (R2.3)

.
}
Encoding Control Files
A control file is a text file that instructs the Java Client how you want your data moved from
source to target for loading or extracting purposes.
Control file characters are encoded in UTF8. UTF8 supports existing control files and allows
non-ASCII characters to be used in newly-created control files.
These areas of the control file can contain non-ASCII values:
• Filenames (source and include)
• SQL identifiers (schema, table, column/field)
• String literals in SQL statements
• Datasource name
• Field delimiter
• Nullstring
• JMS URL
• Startseq
• endseq
• Comments
• Named control file elements including type format, data format, map, source, and job
When the Java 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 Java Client Event and Log File Messages
Event messages that are generated by the Java 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 bin/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 Java 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 Java Client console is also present in the
log file.
46 Configuring Neoview Client Applications