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

DB2CODEPAGE Statement Usage

DB2CODEPAGE Statement Usage

The DB2CODEPAGE statement defines CCSIDs that PowerExchange uses to process data in CHAR and VARCHAR columns during bulk data movement. Each DB2CODEPAGE statement applies to a specific source or target DB2 subsystem.
The DB2CODEPAGE statement has the following syntax:
DB2CODEPAGE=(
db2_subsystem_ssid
[,DB2TRANS={
P
|N|R}]   [,MIXED={
N
|Y}]  [,EBCDIC_CCSID=({
sbcs_ccsid
|
037
} ,{
graphic_ccsid
|
037
} ,{
mixed_ccsid
|
037
})]  [,ASCII_CCSID=({
sbcs_ccsid
|
850
} ,{
graphic_ccsid
|
65534
} ,{
mixed_ccsid
|
65534
})]   [,UNICODE_CCSID=({
sbcs_ccsid
|
367
} ,{
graphic_ccsid
|
1200
} ,{
mixed_ccsid
|
1208
})]  [,PLAN_CCSID=(
sbcs_ccsid
,
graphic_ccsid
,
mixed_ccsid
)] [,REMAP
n
=(
current_data_ccsid
),(
remapped_data_ccsid
) )
You must include the DB2 subsystem SSID. If DB2TRANS=P, you must also include the EBCDIC_CCSID parameter. The other parameters are optional and depend on the code page conversion requirements in your PowerExchange environment. For more information, see DB2CODEPAGE Statement.
For each _CCSID parameter, specify a value for the following types of CCSIDs:
  • A SCCSID for single-byte data.
  • A GCCSID for graphic data.
  • A MCCSID for mixed data that contains both single-byte and double-byte characters.
A value of 65534 indicates no CCSID.
You can define a maximum of 24 DB2CODEPAGE statements in one DBMOVER configuration file for a single PowerExchange Listener.
If PowerExchange connects to a DB2 subsystem that does not have a corresponding DB2CODEPAGE statement, the data is processed with the default code page of the PowerExchange Listener. The PowerExchange Listener reports the code page that is being used.
If data is stored in more than one code page on DB2 or on other file systems that the PowerExchange Listener accesses, you must specify a DB2CODEPAGE statement for each DB2 subsystem that PowerExchange accesses.
For more information about DB2 CCSIDs, see the
IBM DB2 for z/OS Installation Guide
.

0 COMMENTS

We’d like to hear from you!