Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange
  3. DBMOVER Configuration File
  4. Netport Jobs
  5. PowerExchange Message Logs and Destination Overrides
  6. SMF Statistics Logging and Reporting
  7. PowerExchange Security
  8. Secure Sockets Layer Support
  9. PowerExchange Alternative Network Security
  10. PowerExchange Nonrelational SQL
  11. PowerExchange Globalization
  12. Using the PowerExchange ODBC Drivers
  13. PowerExchange Datatypes and Conversion Matrix
  14. Appendix A: DTL__CAPXTIMESTAMP Time Stamps
  15. Appendix B: PowerExchange Glossary

Code Pages That Handle All Supported Unicode Characters

Code Pages That Handle All Supported Unicode Characters

The following table lists ICU code pages that handle all characters supported by Unicode:
Name
Typical Use
Character Length in Bytes
BOCU-1
Email
3+
CESU-8
Compression
3+
IMAP-mailbox-name
Email
3+
SCSU
Compression
3+
UTF-16
-
2
UTF16_OppositeEndian
-
2
UTF16_PlatformEndian
-
2
UTF-16BE
Databases
2
UTF-16LE
Databases
2
UTF-32
-
4
UTF32_OppositeEndian
-
4
UTF32_PlatformEndian
-
4
UTF-32BE
-
4
UTF-32LE
-
4
UTF-7
Email
3+
UTF-8
Databases
3+
Code pages UTF-16 and UTF-32 include a Byte Order marker (BOM) sequence of characters preceding the data. These code pages might be useful in encoding an entire file, but are seldom used in databases where UTF-16BE and UTF-16LE are commonly used or where characters are defined in 16 bit integers.
Little-ended (LE) code pages are used on Linux and Windows systems, for example, UTF-16LE.
Big-ended (BE) code pages are used on Unix, i5/OS and z/OS, for example, UTF-16BE.
PowerExchange does not support supplemental characters defined above the basic plain, that is <U00FFFF>, and which are formed by 2 surrogate NUM16 integers. If PowerExchange encounters a supplemental character, PowerExchange treats it as invalid and replaces it with the substitution character.