A CCSID is a 16-bit number that represents a particular encoding of a specific code page. For example, Unicode is a code page that has several encoding forms, like UTF-8, UTF-16 and UTF-32, but which may or may not actually be accompanied by a CCSID number to indicate that this encoding is being used.
Difference between a code page and a CCSID
The terms code page and CCSID are often used interchangeably, even though they are not synonymous. A code page may be only part of what makes up a CCSID. The following definitions from IBM help to illustrate this point:
A glyph is the actual physical pattern of pixels or ink that shows up on a display or printout.
A character is a concept that covers all glyphs associated with a certain symbol. For instance, "F", "F", "F", "", "", and "" are all different glyphs, but use the same character. The various modifiers do not change the F's essential F-ness.
A character set contains the characters necessary to allow a particular human to carry on a meaningful interaction with the computer. It does not specify how those characters are represented in a computer. This level is the first one to separate characters into various alphabets or ideographic groups. It corresponds to a "character repertoire" in the Unicode encoding model.
A code page represents a particular assignment of code point values to characters. It corresponds to a "coded character set" in the Unicode encoding model. A code point for a character is the computer's internal representation of that character in a given code page. Many characters are represented by different code points in different code pages. Certain character sets can be adequately represented with single-byte code pages, but many require more than that. Examples include JIS X 0208 and Unicode.
An encoding scheme is the byte format of a code page. It maps code point values to sequences of one or more byte values in a computer. For example, UTF-8 and UTF-16BE are two encodings of the same Unicode code page. Meanwhile, in IBM's character data representation architecture, this is typically represented with an ESID. [|EUC] and ISO-2022 are other examples of encoding schemes.
A coded character set identifier contains all of the information necessary to assign and preserve the meaning and rendering of characters through various stages of processing and interchange. This information always includes at least one code page, but may include multiple code pages of differing byte-lengths. The CCSID also has an associated encoding scheme that governs how various code points are to be handled. This mechanism allows a program to recognize bidirectional orientation, character shaping, and other complex encoding information.
Examples
The following examples show how some CCSIDs are made up of other CCSIDs.
Character set
Code page
CCSID
Encoding scheme
01122
00897
897
00370
00301
301
Character set
Code page
CCSID
Encoding scheme
01172
01041
1041
SBCS
00370
00301
301
DBCS
Character set
Code page
CCSID
Encoding scheme
01170
00897
4993
SBCS
00370
00301
301
DBCS
All three of these variant Shift-JIS CCSIDs are multi-byte character sets : the single-byte character set portion of each CCSID is different. The double-byte character set portion is the same across each CCSID. CCSID 5028 uses an updated code page 897 called CCSID 4993. CCSID 932 uses the original code page 897, which is CCSID 897. CCSID 942 uses a different SBCS from the other two CCSIDs, which is 1041. Also notice how CCSID 5028 and 4993 are different by 4096 from the predecessor CCSID with the same code page identifier. This is a common way that CDRA denotes an upgraded CCSID. There are a few reasons for this complexity:
Many of the CCSIDs are used in IBM databases, like DB2, where a database field only supports an SBCS, DBCS or MBCS string. CCSIDs allow programs to differentiate between which one is being used.
When characters are added or replaced, like the Euro currency sign introduction, one can know whether the stored strings support or do not support those character additions because a different CCSID is being used. This versioning is important for the integrity of the data.
It enables reuse of resources among similar CCSIDs.
