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

Type 1 Fallback Mappings and Multibyte Data

Type 1 Fallback Mappings and Multibyte Data

For a PowerCenter session that writes data in a non-IBM code page to a z/OS or i5/OS target system, you might achieve more accurate character conversions by enabling type 1 fallback mappings. To enable type 1 fallback mappings, define USE_TYPE1_FALLBACKS=Y in the DBMOVER configuration file.
For example, if a PowerCenter session writes data from a SQL Server data source to a PowerExchange z/OS target, different Unicode values are used for punctuation characters such as the half-width tilde and the half-width dash. If you do not enable type 1 fallback mappings, this situation can result in substitution characters on the z/OS target. However, if you define USE_TYPE1_FALLBACKS=Y in the DBMOVER file on the Linux, UNIX, or Windows system, the z/OS target receives the closest available match instead of the problem substitution characters.