StarQuest Technical Documents

Error: CCSID 500 is invalid or not supported

Last Update: 26 June 2008
Product: StarSQL
Versions: 5.x
Article ID: SQV00SQ025

Abstract

StarSQL users connecting to DB2 for OS/390 or z/OS may get error messages indicating that CCSID 500 is not valid. These error messages are usually resolved by setting the appropriate ZPARM on DB2 and configuring StarSQL to reflect the appropriate host CCSID value.

Problem

Users connecting to DB2 for OS/390 or z/OS are getting an error message similar to one of the following:

[StarQuest][StarSQL ODBC Driver][DB2]CCSID 500 is unknown or invalid for the datatype or subtype.

[StarQuest][StarSQL ODBC Driver][DB2]CCSID 500 not supported by this version of the database server.

Solution

During the installation of DB2, CCSID parameters are set in the installation panel DSNTIPF. These ZPARMS may also be modified after installation.

The SCCSID operand of the DSNHDECP macro is set to 0 by default. This may need to be changed to the CCSID for your country. For American English systems, this value should be set to 37.

Note: In DB2 5.x, three new parameters ASCCSID, AMCCSID, and AGCCSID were added. If you are using ASCII tables, you may also need to set the ASCCID value; use 437 for American English.

If you get this error and the SCCSID ZPARM on DB2 already reflects the language of your country, you may need to configure StarSQL to use that CCSID. You do this by editing the StarSQL data source configuration. Instructions follow:

  1. Open the StarSQL data source configuration and go to the Experts Page.
  2. Set the AutoTypDefOvr value to one appropriate for your host. For example, in the Czech Republic the DB2 SCCSID ZPARM is 870 and you would set AutoTypDefOvr to 870,0,0.

Note: If this error occurs in a double-byte system, additional changes may be necessary. Please consult your IBM documentation. If you have purchased maintenance, you may also contact StarQuest Customer Support for additional information.

References

DB2 for OS/390 V5 Installation Guide
- Section 2.5.18 Application Programming Defaults Panel 1: DSNTIPF
- Section B.2 Specifying a System Coded Character Set Identifier

Sample for DB2 5.x

The following listing is part of the DSNTIJUZ job from the SDSNSAMP JCL library on DB2 5.x. This is only a sample.

000202 //******************************************************************
000203 //* ASSEMBLE AND LINK EDIT DATA-ONLY LOAD MODULE DSNHDECP.
000204 //* THE FOLLOWING STEPS ARE NEEDED ONLY IF THE
000205 //* VALUES ARE CHANGED FROM THOSE WHICH ARE SHIPPED.
000206 //******************************************************************
000207 //DSNTIZP EXEC PGM=ASMA90,PARM='OBJECT,NODECK',COND=(4,LT)
000208 //SYSLIB DD DISP=SHR,
000209 // DSN=DSN510.SDSNMACS
000210 //SYSLIN DD DSN=&&LOADSET(DSNHDECA),DISP=(NEW,PASS),UNIT=SYSDA,
000211 // SPACE=(80,(50,50,2)),DCB=(BLKSIZE=80)
000212 //SYSPRINT DD SYSOUT=*
000213 //SYSUDUMP DD SYSOUT=*
000214 //SYSUT1 DD UNIT=SYSDA,SPACE=(800,(50,50),,,ROUND)
000215 //SYSUT2 DD UNIT=SYSDA,SPACE=(800,(50,50),,,ROUND)
000216 //SYSUT3 DD UNIT=SYSDA,SPACE=(800,(50,50),,,ROUND)
000217 //SYSIN DD *
000218 DSNHDECM CHARSET=ALPHANUM, X
000219 ASCCSID=437, X
000220 AMCCSID=65534, X
000221 AGCCSID=65534, X
000222 SCCSID=37, X
000223 MCCSID=65534, X
000224 GCCSID=65534, X
000225 ENSCHEME=EBCDIC, X
000226 DATE=ISO, X
000227 DATELEN=0, X
000228 DECARTH=DEC15, X
000229 DECIMAL=PERIOD, X
000230 DEFLANG=C, X
000231 DELIM=DEFAULT, X
000232 MIXED=NO, X
000233 SQLDELI=DEFAULT, X
000234 DSQLDELI=APOST, X
000235 SSID=DSN5, X
000236 STDSQL=NO, X
000237 TIME=ISO, X
000238 TIMELEN=0
000239 END
000240 //*

 


DISCLAIMER

The information in technical documents comes without any warranty or applicability for a specific purpose. The author(s) or distributor(s) will not accept responsibility for any damage incurred directly or indirectly through use of the information contained in these documents. The instructions may need to be modified to be appropriate for the hardware and software that has been installed and configured within a particular organization.  The information in technical documents should be considered only as an example and may include information from various sources, including IBM, Microsoft, and other organizations.