The information in this section provides a summary of the steps required. For further information, refer to the IBM DRDA Connectivity Guide, SC26-4783, and the documentation provided for your host RDBMS and operating system.
On an OS/390 or MVS system, the host CCSID cannot be queried when set. The system setup file DSNHDECP contains code page and character set related system parameters:
Example for "US English":
SCCSID set to 37 (leading zeros not required) MCCSID set to 65534 GCCSID set to 65534
Example for "Japanese English":
SCCSID set to 1027 MCCSID set to 5035 GCCSID set to 4396
To change the settings, ask your OS.390 or MVS system administrator to:
The system-wide CCSID setting normally defaults to 65535, which indicates no character conversion. The DB2 Connect workstation cannot connect to an AS/400 system if this setting is used.
When a connection is made to DB2/400, there is a user profile that the corresponding job runs under. Individual users have a user profile, in which one of the settings is CCSID. This defaults to *SYSVAL.
For DB2 Connect to successfully connect, either the system-wide CCSID setting must be changed to some value other than 65535, or the CCSID attribute of the user's user profile must be set to some value other than *SYSVAL.
For US English, set the user profile CCSID value to 37. For other languages, see the appendix entitled "National Language Version Default System Values", in AS/400 National Language Support, SC41-3101, which lists supported languages and CCSIDs for the AS/400.
For double byte characters, OS/400 must be enabled for DBCS, and the CCSID must be set to a "mixed" value from which the other codes required can be derived.
Refer to your AS/400 system administrator and documentation for further information.
With DB2 for VM and VSE, the parameter CHARNAME is set when the database is started. This parameter is set at the database level, and it can be queried by viewing the system table SYSTEM.SYSOPTIONS.
DB2 for VM and VSE provides a list of possible values for CHARNAME. For example, for Japanese English, set CHARNAME to the string Japanese_English. For US English (CCSID 37), set CHARNAME to English. For CCSID 500, set CHARNAME to International.
Note that, in addition to database level tagging, DB2 for VM and VSE also provides column level CCSID tagging. All the data inside a database need not have the same CCSID. For example, in a single table one column could be tagged with CCSID 500, another tagged with 277, and so on.
Also, DB2 for VM and VSE does not currently provide support for host code pages 1026 or 931, neither does it provide support for several of the conversions listed earlier, namely:
Code Host Page CCSID 1004 037, 273, 277, 278, 280, 284, 285, 297, 500, 871 1051 037, 273, 277, 278, 280, 284, 285, 297, 500, 871 1046 420 1089 420 Any of the Macintosh code pages (1275, 1280, 1281, 1282, 1283)
Refer to your DB2 for VM and VSE Database Administrator and documentation for further information.