ICUCNVPROPERTY=(
CPN
               ,
property
               ,
value
)

CPN

Required. The code page slot number for which to define a property. Valid values are from 301 through 340.

To identify available code page slots, see the ICUCHECK report.

property

Required. Enter one of the following options:

ASCII.
Indicates that the characters 0 to 9 and A through Z match the 7-bit ASCII values, such as in code page US_ASCII. For example:
ICUCNVPROPERTY=(301,ASCII,ON)
BUFFER_INCREMENT.
PowerExchange allocates extra bytes for the buffer when converting to the code page. Enter a numeric value for this property.
For example:
ICUCNVPROPERTY=(301,BUFFER_INCREMENT,8)
EBCDIC.
Indicates that the characters 0 to 9 and A through Z match the standard EBCDIC values, such as in code page IBM-37.
For example:
ICUCNVPROPERTY=(301,EBCDIC,ON)
FIX_MIN_LENGTH.
ICU processing drops leading binary zeros when converting to double-byte code pages. PowerExchange creates all characters at the correct minimum length and inserts leading binary zeros as needed.
The Show a code page uses this property.
For example:
ICUCNVPROPERTY=(301,FIX_MIN_LENGTH,ON)
IBM420_END_OF_WORD_SPACES.
Adds a space after certain IBM420 characters that end words.
For example:
ICUCNVPROPERTY=(301,IBM420_END_OF_WORD_SPACES,ON) 
LOWERCASE_NONSTANDARD.
On z/OS, four Japanese code pages include lowercase a through z characters that do not match the standard EBCDIC value that code page IBM-37 uses.
For these code pages, the client program converts the SQL to uppercase before PowerExchange converts the SQL to the z/OS code page. CP930 uses this property.
For example:
ICUCNVPROPERTY=(301,LOWERCASE_NONSTANDARD,ON)
POWERCENTER_NAME.
Defines a PowerCenter name for the code page. The name must match an entry in the list on the define relational sources page in the Workflow Manager.
On Windows, to use an ICU code page with ODBC, define a PowerCenter name for the code page.
For example:
ICUCNVPROPERTY=(301,POWERCENTER_NAME,"IBM EBCDIC Japanese")
REVERSE_EBCDIC_DIGITS.
Reverses consecutive sequences of the following bytes: F0, F1, F2, F3, F4, F5, F6, F7, F8, and F9.
For example:
ICUCNVPROPERTY=(301,REVERSE_EBCDIC_DIGITS,ON)
SQL_PARSABLE.
Indicates that the invariant SQL characters must match the standard values for the ASCII or EBCDIC type. Use this property to determine whether the ODBC layer needs to translate SQL before searching for literals like SELECT, FROM, or WHERE.
For example:
ICUCNVPROPERTY=(301,SQL_PARSABLE,ON)
STATE_BYTES.
PowerExchange allocates two extra bytes for the buffer when converting to the code page.
For example:
ICUCNVPROPERTY=(301,STATE_BYTES,ON)
UNKNOWN_ENDIANNESS.
Indicates that the code page has a different integer endianness, based on the system.
For example:
ICUCNVPROPERTY=(301,UNKNOWN_ENDIANNESS,ON)
In some situations, the system can determine the correct code page. For example, switch from UTF-16 to UTF-16LE on Windows. Generally, however, avoid such code pages.
UNSHAPE_ARABIC.
Converts Unicode characters derived from IBM420 “shaped” characters to characters for Windows 1256. Converts Unicode characters from 0xFE70 through 0xFEF4 to equivalent 0x62
xx
characters. Converts LAM ALEF ligature characters from 0xFEF5 through 0xFEFC to the Unicode 0x0644 character and another character.
For example:
ICUCNVPROPERTY=(301,UNSHAPE_ARABIC,ON)
USE_TYPE1_FALLBACKS.
Enables type 1 fallback mappings for the specified code page.
For example:
ICUCNVPROPERTY=(242,USE_TYPE1_FALLBACKS,ON) 
Default is OFF.
To enable type 1 fallback mappings for all code pages, use the USE_TYPE1_FALLBACKS DBMOVER statement.

If you specify a property that is not valid, an error message displays the list of valid properties.

value

Required. The value for the property, as follows:

For binary properties, either ON or OFF.
For new customer ICU code pages, default is OFF.
For BUFFER_INCREMENT, a numeric value.
For new customer ICU code pages, default is 0.