Reference Manual

10.5.2
- 10.5.5
- 10.5.4
- 10.5.3
- 10.5.1
- 10.5
- 10.4.1
- 10.4.0 HotFix 1
- 10.4.0

Back Next

PowerExchange Control Table for ICU Code Pages Sample Report

The following sample report shows the PowerExchange control table for ICU code pages.

Report 2 : Power Exchange control table for ICU code pages
==========================================================

NUM_STATIC_CODEPAGES     =  41
number of ICU code pages = 300
------------------------------
NUMBER_OF_CODEPAGES      = 341

Min    : Minimum bytes per character
Max    : Maximum bytes per character
In     : Increment to column size on top of standard formula
              column_size = to_max / (float)fr_min + 0.5)
Al     : Number of aliases

L      : Length of the space character
Space  : Hex of the space character used to pad CHAR columns

Flag 1 : S = Are States Used
Flag 2 : U = Endianness Unknown
Flag 3 : A = ASCII, E = EBCDIC
Flag 4 : P = SQL is parsable without translation
Flag 5 : L = Lower case not standard for ASCII/EBCDIC SQL
Flag 6 : X = Supplemental characters beyond UCS_2 plain

CPN Converter name  Min Max In Al L Space  Flags   PMlocale    PowerCenter Name
--- --------------  --- --- -- -- - -----  -----   --------    -----------------
041 UTF-8           1   3   0 10 1 20         A P  X  UTF-8    UTF-8 encoding of Unicode 
042 UTF-16          2   2   2  0 2 0020     U      X  UTF-16   UTF-16 encoding of Unicode 
043 UTF-16BE        2   2   0 11 2 0020            X  UTF-16BE UTF-16 encoding of Unicode (Big Endian) 
....

The following table describes the fields in the report:

Field	Description
CPN	PowerExchange code page number.
Converter name	ICU converter name.
Min	Minimum bytes per character.
Max	Maximum bytes per character.
In	Increment added to the buffer size in addition to the standard formula. This increment allows space for leading escape sequences on code pages.
Al	Number of aliases for this code page.
L	Length of the space character.
Space	Hexadecimal value of the space character that is used to pad CHAR columns.
Flag 1 : States	Set to S if state bytes are used. For example: X'0E', X'0F' in EBCDIC mixed-length code pages Code pages with sub-versions such as ISO2022 and ISCII
Flag 2 : Endianness unknown	Set to U if the code page takes a different meaning depending on the endian format of integers. For example, UTF-16 on Windows means UTF-16LE, but UTF-16 on z/OS means UTF-16BE.
Flag 3 : ASCII / EBDIC	Set to A if characters 0 through 9 and A through Z are compatible with 7-bit ASCII. Set to E if characters 0 through 9 and A through Z are compatible with standard EBCDIC, such as IBM-37.
Flag 4 : Parsable without translation	Set to P if the invariant SQL characters are consistent with the standard for the ASCII / EBCDIC type. This flag is used within the ODBC layer to determine whether SQL is understandable on that system. For example, if PowerCenter passes SQL in IBM EBCDIC Japanese CP939 to a Windows program compiled in code page ISO-8859, the SQL must be translated into an ASCII code page before key words like “select,” “from,” “where” can be recognized.
Flag 5: Lower case non-standard	Set to L if lowercase a to z characters are not consistent with standard EBCDIC such as IBM-37. This problem affects some Japanese code pages. Sometimes this problem is handled by forcing SQL into uppercase before converting it.
Flag 6: Supplemental Characters	Set to X if the code page includes supplemental characters beyond UCS_2.
PMlocale	Name of the code page as it is understood by PowerCenter.
PowerCenter Name	PowerCenter name of the code page. Data can be passed between PowerExchange and PowerCenter in this code page.

Rename Saved Search

Table of Contents

Reference Manual

Reference Manual

PowerExchange Control Table for ICU Code Pages Sample Report

PowerExchange Control Table for ICU Code Pages Sample Report