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

DB2DEF_ENCODING Statement

DB2DEF_ENCODING Statement

The DB2DEF_ENCODING statement defines the default encoding scheme that PowerExchange assigns to any DB2 columns that do not have an encoding scheme when you create a DB2 data map.
z/OS
DB2 for z/OS
DB2CODEPAGE
No
DB2DEF_ENCODING={A|
E
|U}
  • A.
    ASCII encoding.
  • E
    .
    EBCDIC encoding.
  • U.
    Unicode encoding.
Default is E.
  • An encoding scheme might not be specified in the SYSIBM.SYSDATABASE table as a result of multiple DB2 migrations.
  • In general, specify the encoding that is defined for DB2 in the
    DEF ENCODING SCHEME
    field on the application programming defaults panel,
    DSNTIPF
    . However, if DSNTIPF specifies 65534 for the mixed code page, edit the DB2CODEPAGE statement to set the
    mixed_ccsid
    value of the comparable ASCII, EBCDIC, or Unicode parameter to 037. The 037 value is required for PowerExchange to read the DB2 catalog tables.
    For example, if you use the default value of E for the DB2DEF_ENCODING statement and the DSNTIPF panel specifies 65534 for the EBCDIC mixed code page, specify 037 as the last positional subparameter of the EBCDIC_CCSID parameter in the DB2CODEPAGE statement:
    EBCDIC_CCSID=(
    sbcs_ccsid
    ,
    graphic_ccsid
    ,037)

0 COMMENTS

We’d like to hear from you!