Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange Utilities
  3. createdatamaps - Data Map Creation Utility
  4. DTLCCADW - Adabas PCAT Utility
  5. DTLCUIML - IMS Log Marker Utility
  6. DTLINFO - Release Information Utility
  7. DTLREXE - Remote Execution Utility
  8. DTLUAPPL - Restart Token Utility
  9. DTLUCBRG - Batch Registration Utility
  10. DTLUCDEP - CDEP Maintenance Utility
  11. DTLUCSR2 - IDMS SR2 and SR3 Records Utility
  12. DTLUCUDB - DB2 for Linux, UNIX, and Windows CDC Utility
  13. DTLULCAT and DTLULOGC - IDMS Log Catalog Utilities
  14. DTLURDMO - Data Map Utility
  15. DTLUTSK - Task Control Utility
  16. EDMLUCTR - Log Scan and Print Utility
  17. EDMXLUTL - Event Marker Utility
  18. HOSTENT - TCP/IP Address Reporter Utility
  19. PWXCATMY - MySQL Catalog Utility
  20. PWXUCCLPRT - Print Log Summary Utility
  21. PWXUCDCT - Logger for Linux, UNIX, and Windows Utility
  22. PWXUCREG - Capture Registration Suspend Utility
  23. PWXUCRGP - Capture Registrations Print Utility
  24. PWXUDMX - Data Maps Update Time ECSA Memory Utility
  25. PWXUGSK - SSL Reporting Utility for z/OS
  26. PWXUMAP - Map List Utility
  27. PWXUSSL - PowerExchange SSL Reporting Utility

DTLUCBRG Code Page Processing

DTLUCBRG Code Page Processing

DTLUCBRG disregards the CODEPAGE statement in the DBMOVER configuration file and instead uses the code page that is used to store registrations and capture data map metadata, as follows:
  • IBM037 on i5/OS
  • IBM1047 on z/OS
  • UTF-8 on Linux, UNIX, or Windows
Whenever the DBMOVER CODEPAGE statement is overridden, PowerExchange issues the following message:
Changed client code pages to
name
(
internal_code_page_number
)
On i5/OS and z/OS, PowerExchange supports table and column names with characters that are present in code pages IBM037 and IBM1047, respectively. Accented characters that are not in the code pages are not supported. On Linux, UNIX, and Windows, all characters are supported.
When the PowerExchange Listener retrieves data, code page conversion of SQL and data is performed automatically. For example, a PowerExchange Listener on z/OS might need to use a particular SQL code page to meet the requirements of a DB2 subsystem. SQL is converted to the required code page and is received by the Listener ready for use by DB2. Column data is described according to the DB2 CCSIDs and sent back to DTLUCBRG, which converts it to the required metadata code page.

0 COMMENTS

We’d like to hear from you!