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

Adding a Custom ICU Code Page

Adding a Custom ICU Code Page

PowerExchange defines code pages internally using Code Page Numbers (CPNs). You can use the ICUCHECK utility to list the defined CPNs.
User-defined ICU code pages must be defined in slots 301 to 340.
Add a custom code page on each system that is involved in PowerExchange change data capture or bulk data movement. For example, if you are moving data from a data source on z/OS to a target on UNIX, you must add a code page definition to the DBMOVER configuration file on the z/OS system and on the UNIX system.
You must also add the new code page to the dbmover.cfg file on Windows so that you can view the data from the PowerExchange Navigator when performing a row test.
To add a custom ICU code page:
  1. Move the CNV file to the required directories on each system.
    The following table lists where CNV files are located for each system:
    System
    Location of CNV Files
    i5/OS
    UNIX style directory.
    The makeconv utility is run from the QSH shell.
    Set ICUDATADIR to the directory name.
    UNIX and Linux
    CNV files are located in the PowerExchange installation directory.
    If PowerCenter workflows are run on the machine, you must copy the CNV files to the server/bin directory which also contains the RES files.
    Windows
    CNV files are located in the PowerExchange installation directory.
    If PowerCenter workflows are run on the machine, you must copy the CNV files to the server/bin directory which also contains the RES files.
    z/OS
    UNIX style directory.
    The makeconv utility is run from USS.
    Set ICUDATADIR to the directory name.
  2. Run ICUCHECK to determine which code pages are defined and to verify that the current configuration and dynamic link libraries are correct. Add the ICUDATADIR statement to the DBMOVER configuration file. In this file, specify the location of the CNV file.
  3. Add an ICUCONVERTER(
    cpn
    ,ADD...) statement to the DBMOVER configuration file. Typically, the first user-defined ICU code page uses CPN 301, the next one uses 302, and so on.
  4. If the code page is used by DB2 to map a CCSID to a code page, add an ICUALIAS=(
    cpn
    ,ADD...) statement to the DBMOVER configuration file.
  5. If the code page replaces an existing code page that is used by DB2 to map a CCSID to a code page, add an ICUALIAS=(
    cpn
    ,DELETE...) statement to the DBMOVER configuration file.
    Consult the ICUCHECK reports to determine the CPN of the existing code page.
  6. Run ICUCHECK again to verify that the syntax of the PowerExchange configuration statements is correct and that the CNV file can be loaded. ICUCHECK does not start if the parameters contain syntax errors.