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. DTL__CAPXTIMESTAMP Time Stamps
  15. PowerExchange Glossary

DB2CODEPAGE Statement

DB2CODEPAGE Statement

The DB2CODEPAGE statement defines the single-byte, graphic, and mixed CCSIDs that PowerExchange uses to process CHAR and VARCHAR column data in a DB2 for z/OS subsystem that is involved in bulk data movement.
z/OS
DB2 for z/OS
No
DB2CODEPAGE=(
db2_subsystem
[,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
|
037
} ,{
graphic_ccsid
|
037
} ,{
mixed_ccsid
|
037
})] [,REMAP
n
=(
current_data_ccsid
),(
remapped_data_ccsid
) )
db2_subsystem
Required. The DB2 subsystem identifier (SSID) of a source or target subsystem.
DB2TRANS={
P
|N|R}
Indicates whether DB2 translates the encoding of data that it passes to or receives from PowerExchange. Options are:
  • P
    . DB2 translates the code pages in which column data is stored into the code pages defined in the DB2 plan that was bound for PowerExchange. You must also specify the EBCDIC_CCSID parameter and optionally the PLAN_CCSID parameter. If you specify both, the PLAN_CCSID parameter takes precedence. If you have ASCII and Unicode data, you can also specify the ASCII_CCSID and UNICODE_CCSID parameters to map to the EBCDIC code pages.
    To use any of the *_CCSID parameters, you must set DB2TRANS to P.
  • N
    . DB2 does not translate the code pages of the column data to equivalent EBCDIC code pages. PowerExchange uses the native code page in which the data is stored. You do not need to define the EBCDIC_CCSID, ASCII_CCSID, UNICODE_CCSID, or PLAN_CCSID parameters.
  • R
    . DB2 translates certain user-specified data code pages to other code pages, as defined in one or more REMAP
    n
    parameters. In each REMAP
    n
    parameter, the first positional parameter identifies a data code page to remap, and the second positional parameter identifies the code page to use. Use a code page other than the code page in which the PowerExchange DB2 plan is bound.
Default is P.
MIXED={
N
|Y}
Indicates whether DB2 columns contain ASCII and EBCDIC character strings with mixed data and graphic data. Mixed data consists of both single-byte and double-byte characters, and graphic data consists of double-byte characters.
Options are:
  • N.
    Columns with ASCII and EBCDIC character strings contain only single-byte (SBCS) data. Mixed and graphic data does not occur.
  • Y.
    Columns with ASCII and EBCDIC character strings contain mixed data and graphic data.
Default is N.
EBCDIC_CCSID=({
sbcs_ccsid
|
037
},{
graphic_ccsid
|
037
},{
mixed_ccsid
|
037
})
Required if DB2TRANS=P (the default). The CCSIDs to use for EBCDIC single-byte, graphic double-byte, and mixed (single-byte and double-byte) data.
Valid values are from 1 through 65534 for each positional subparameter. A value of 65534 indicates no CCSID.
The default values of 037,037,037 are used if you do not specify the DB2CODEPAGE statement or if you accept the values from the z/OS Installation Assistant without modification. If you changed these values during installation, the Installation Assistant customizes the DB2CODEPAGE statement in the DBMOVER file with the values you entered.
If an EBCDIC code page does not have an ICU conversion table, or if the EBCDIC code page is different from the one in which the DB2 plan for PowerExchange is bound, you can use the PLAN_CCSID parameter to map to another EBCDIC code page that does have an ICU conversion table or that reflects the DB2 plan.
DB2 delivers data to PowerExchange in an EBCDIC code page even if the data is physically stored in an ASCII or Unicode code page. The DB2 catalog tables are stored in UTF-8, which corresponds to CCSID 1208. This CCSID is remapped from the UNICODE_CCSID
mixed_ccsid
code page value to the EBCDIC_CCSID
mixed_ccsid
code page value.
On single-byte systems, either repeat the SBCS code page three times or use 65534 with the MIXED=N parameter. For example:
EBCDIC_CCSID=(1047,1047,1047)
or
DB2CODEPAGE=(D91G,EBCDIC_CCSID=(1047,65534,65534),MIXED=N)
PowerExchange then uses the single-byte EBCDIC code page.
ASCII_CCSID=({
sbcs_ccsid
|
850
},{
graphic_ccsid
|
65534
},{
mixed_ccsid
|
65534
})
Optional. The CCSIDs to use for ASCII single-byte, graphic, and mixed data. Specify this parameter only if your subsystem contains ASCII encoded data that is involved in bulk data movement. PowerExchange maps these ASCII code pages to equivalent EBCDIC code pages that are defined in the EBCDIC_CCSID parameter. Also include the EBCDIC_CCSID parameter.
Valid values are from 1 through 65534 for each subparameter. A value of 65534 indicates no CCSID.
The z/OS Installation Assistant inserts the values 850,65534,65534 unless you change them during installation.
UNICODE_CCSID=({
sbcs_ccsid
|
367
},{
graphic_ccsid
|
1200
},{
mixed_ccsid
|
1208
})
Optional. The CCSIDs for Unicode single-byte, graphic, and mixed data. PowerExchange maps these Unicode code pages to equivalent EBCDIC code pages that are defined in the EBCDIC_CCSID parameter. Also include the EBCDIC_CCSID parameter.
Valid values are from 1 through 65534 for each subparameter. A value of 65534 indicates no CCSID.
The default values of 367,1208,1200 are used if you do not specify the DB2CODEPAGE statement or if you accepted the z/OS Installation Assistant values without modification. Usually, these default values are suitable.
In DB2 Verson 8.1 and later, the DB2 catalog tables are stored in UTF-8, which corresponds to CCSID 1208.
PLAN_CCSID=({
sbcs_ccsid
|
037
},{
graphic_ccsid
|
037
},{
mixed_ccsid
|
037
})
Optional. The CCSIDs to use for EBCDIC single-byte, graphic, and mixed data instead of those in the EBCDIC_CCSID parameter. Use this parameter when you need to redirect the EBCDIC code pages to other EBCDIC code pages.
For example, use this parameter in the following situations:
  • The EBCDIC_CCSID code pages do not have an ICU conversion table that PowerExchange can use for ICU-based code page conversion.
  • The EBCDIC_CCSID code pages match the default code pages that were defined for the DB2 subsystem but differ from the EBCDIC code pages for a particular source or target table.
Default is 037,037,037.
REMAP
n
=(
current_data_ccsid
,
remapped_data_ccsid
)
Optional. If you specified DB2TRANS=R, you can use this parameter to have DB2 remap the code page in which the data is stored to another code page that you specify. For example, if you have ASCII data that does not map to the code page in which the DB2 plan is bound and that does not have an ICU convertor, use this parameter to remap the ASCII code page to a supported EBCDIC code page.
Alternatively, if you specified DB2TRANS=N, DB2 does not translate or remap the data. However, PowerExchange can use the REMAP
n
statement to substitute the correct code page for the incorrect one. For example, DB2 might report a data code page that does not match the code page defined in the DB2 catalog, possibly because the data was loaded incorrectly. In this case, you can specify the correct code page in the REMAP
n
parameter.
You can specify up to six REMAP
n
parameters in a DB2CODEPAGE statement, each for a different DB2 table. Increment the
n
number at the end of the parameter names so that each name is unique.
  • If a PowerExchange Listener connects to a DB2 subsystem for which there is no DB2CODEPAGE statement, PowerExchange uses the code page of the PowerExchange Listener.
  • During PowerExchange installation, a bind job binds the DB2 plan for PowerExchange as EBCDIC, without specifying the CCSIDs. As a result, PowerExchange uses the default application programming CCSIDs that were defined for the DB2 subsystem when it was created. PowerExchange retrieves these CCSIDs from the DB2 catalog tables and uses them along with the DB2CODEPAGE parameters to determine the code page to use.
  • The values that you define for the DB2CODEPAGE statement must match the values that were specified for the DB2 subsystem on the application programming defaults panel, DSNTIPF. If you did not specify a value for the graphic and mixed CCSIDs in DB2, specify 65534 for the
    graphic_ccsid
    and
    mixed_ccsid
    parameters in the DB2CODEPAGE statement.
    If the CCSIDs that you specified for the DB2 subsystem differ from the DB2CODEPAGE default CCSIDs, you must edit the DB2CODEPAGE statement to match the DB2 CCSIDs.
    The following table shows the DB2 configuration options on the DSNTIPF panel and the DSNHDECP load module that correspond to the DB2CODEPAGE parameters:
    DB2CODEPAGE Parameter
    DSNTIPF Field
    DSNHDECP Parameter
    EBCDIC_CCSID
    EBCDIC CCSID
    SCCSID (single-byte), MCCSID (mixed), GCCSID (graphic)
    ASCII_CCSID
    ASCII CCSID
    ASCCSID (single-byte), AMCCSID (mixed) AGCCSID (graphic)
    UNICODE_CCSID
    UNICODE CCSID
    USCCSID (single-byte), UMCCSID (mixed), UGCCSID (graphic)
    MIXED
    MIXED DATA
    MIXED
    For more information about CCSID values and their meanings, see the IBM
    DB2 for z/OS Installation Guide
    for the DB2 version.
  • If you click
    Advanced Parms
    on the
    DB2 Parameters
    page of the z/OS Installation Assistant, you can enter CCSID values for the following parameters:
    • DB2CODEPAGE_ASCII_DBCS_CCSID
    • DB2CODEPAGE_ASCII_MIXED_CCSID
    • DB2CODEPAGE_ASCII_SBCS_CCSID
    • DB2CODEPAGE_EBCDIC_DBCS_CCSID
    • DB2CODEPAGE_EBCDIC_MIXED_CCSID
    • DB2CODEPAGE_EBCDIC_SBCS_CCSID
    • DB2CODEPAGE_MIXED
    • DB2CODEPAGE_UNICODE_DBCS_CCSID
    • DB2CODEPAGE_UNICODE_MIXED_CCSID
    • DB2CODEPAGE_UNICODE_SBCS_CCSID
    These installation parameters populate the EBCDIC_CCSID, ASCII_CCSID, and UNICODE_CCSID parameters in the DB2CODEPAGE statement of the DBMOVER file. You can edit them in the DBMOVER file if necessary.
  • PowerExchange automatically generates a minimal DB2CODEPAGE specification that includes the UNICODE_CCSID and EBCDIC_CCSID parameters if no DB2CODEPAGE parameters are defined. The UNICODE_CCSID is included because DB2 catalog tables use Unicode encoding.
  • The DB2CODEPAGE statement applies to bulk data movement operations only. For DB2 CDC, PowerExchange always uses the native code page of the DB2 data.
  • The DB2CODEPAGE statement does not affect the CODEPAGE statement. If you use the DB2DEF_ENCODING statement, in certain cases, you might need to edit the DB2CODEPAGE statement to set the
    mixed_ccsid
    value to 037 in the ASCII_CCSID, EBCDIC_CCSID, or UNICODE_CCSID parameter that corresponds to the DB2DEF_ENCODING option.
  • If PowerExchange tries to read columns that contain VARGRAPHIC or LOB data in a table on a single-byte subsystem, and the default DB2CODEPAGE setting of DB2TRANS=P is in effect, the you might receive the following SQL error:
    -332
    CHARACTER CONVERSION BETWEEN CCSID
    from_ccsid
    TO
    to_ccsid
    REQUESTED BY
    reason_code
    IS NOT SUPPORTED
    If this situation occurs, specify DB2TRANS=N in the DB2CODEPAGE statement.