Table of Contents

Search

  1. Preface
  2. Working with Transformations
  3. Aggregator Transformation
  4. Custom Transformation
  5. Custom Transformation Functions
  6. Data Masking Transformation
  7. Data Masking Examples
  8. Expression Transformation
  9. External Procedure Transformation
  10. Filter Transformation
  11. HTTP Transformation
  12. Identity Resolution Transformation
  13. Java Transformation
  14. Java Transformation API Reference
  15. Java Expressions
  16. Java Transformation Example
  17. Joiner Transformation
  18. Lookup Transformation
  19. Lookup Caches
  20. Dynamic Lookup Cache
  21. Normalizer Transformation
  22. Rank Transformation
  23. Router Transformation
  24. Sequence Generator Transformation
  25. Sorter Transformation
  26. Source Qualifier Transformation
  27. SQL Transformation
  28. Using the SQL Transformation in a Mapping
  29. Stored Procedure Transformation
  30. Transaction Control Transformation
  31. Union Transformation
  32. Unstructured Data Transformation
  33. Update Strategy Transformation
  34. XML Transformations

Transformation Guide

Transformation Guide

Code Page Compatibility

Code Page Compatibility

When the Integration Service runs in ASCII mode, it passes data to the Custom transformation procedure in ASCII. When the Integration Service runs in Unicode mode, it passes data to the procedure in UCS-2.
Use the INFA_CTChangeStringMode() and INFA_CTSetDataCodePageID() functions in the Custom transformation procedure code to request the data in a different format or in a different code page.
The functions you can use depend on the data movement mode of the Integration Service:
  • ASCII mode.
    Use the INFA_CTChangeStringMode() function to request the data in UCS-2. When you use this function, the procedure must pass only ASCII characters in UCS-2 format to the Integration Service. You cannot use the INFA_CTSetDataCodePageID() function to change the code page when the Integration Service runs in ASCII mode.
  • Unicode mode.
    Use the INFA_CTChangeStringMode() function to request the data in MBCS (multi-byte character set). When the procedure requests the data in MBCS, the Integration Service passes data in the Integration Service code page. Use the INFA_CTSetDataCodePageID() function to request the data in a different code page from the Integration Service code page. The code page you specify in the INFA_CTSetDataCodePageID() function must be two-way compatible with the Integration Service code page.
You can also use the INFA_CTRebindInputDataType() function to change the format for a specific port in the Custom transformation.

0 COMMENTS

We’d like to hear from you!