This article includes a list of references, but its sources remain unclear because it has insufficient inline citations. Please help to improve this article by introducing more precise citations. (February 2012)

Extended Binary Coded Decimal Interchange Code (EBCDIC) is an 8-bit character encoding used mainly on IBM mainframe and IBM midrange computer operating systems.

EBCDIC descended from the code used with punched cards and the corresponding six bit binary-coded decimal code used with most of IBM's computer peripherals of the late 1950s and early 1960s.

It is also employed on various non-IBM platforms such as Fujitsu-Siemens' BS2000/OSD, HP MPE/iX, and Unisys MCP.

History[link]

EBCDIC ( /ˈɛbsɨdɪk/) was devised in 1963 and 1964 by IBM and was announced with the release of the IBM System/360 line of mainframe computers. It is an 8-bit character encoding, in contrast to, and developed separately from, the 7-bit ASCII encoding scheme. It was created to extend the existing binary-coded decimal (BCD) interchange code, or BCDIC, which itself was devised as an efficient means of encoding the two zone and number punches on punched cards into 6 bits.

While IBM was a chief proponent of the ASCII standardization committee,^[1] they did not have time to prepare ASCII peripherals (such as card punch machines) to ship with its System/360 computers, so the company settled on EBCDIC.^[2] The System/360 became wildly successful, and thus so did EBCDIC.

All IBM mainframe and midrange peripherals and operating systems use EBCDIC as their inherent encoding,^[3] but AIX running on the iSeries, Linux running on the zSeries, and the IBM PC and its descendants use ASCII. Software and many hardware peripherals can translate to and from encodings, and modern mainframes (such as IBM zSeries) include processor instructions, at the hardware level, to accelerate translation between character sets.

EBCDIC has no modern technical advantage over ASCII-based code pages such as the ISO-8859 series or Unicode. There are some technical niceties in each, e.g., ASCII and EBCDIC both have one bit which indicates upper or lower case. But there are some aspects of EBCDIC which make it much less pleasant to work with than ASCII, such as a non-contiguous alphabet. As with single-byte extended ASCII codepages, most EBCDIC codepages only allow up to two languages^{[citation needed]} (English and one other language) to be used in a database or text file.

Where true support for multilingual text is desired, a system supporting far more characters is needed. Generally this is done with some form of Unicode support. There is an EBCDIC Unicode Transformation Format called UTF-EBCDIC proposed by the Unicode consortium, but it is not intended to be used in open interchange environments and, even on EBCDIC-based systems, it is almost never used. IBM mainframes support UTF-16, but they do not support UTF-EBCDIC natively.

Arabic EBCDIC versions are typically in presentation order, in left to right order as displayed by an older mainframe or line printer, rather than in the right to left logical order used by modern encodings such as Unicode.

Codepage layout[link]

The table below is based on CCSID 500, one of the code page variants of EBCDIC; it shows only the basic (English) EBCDIC characters. Characters 00–3F and FF are controls, 40 is space, 41 is no-break space (RSP: "Required Space"), E1 is numeric space (NSP: "Numeric Space"), and CA is soft hyphen. Characters are shown with their equivalent Unicode codes. Invariant alphanumeric, punctuation, and control characters common to all EBCDIC code pages are shown in bold. Unassigned codes are typically filled with international or region-specific characters in the various EBCDIC code page variants.

Criticism and humor[link]

Open-source-software advocate and hacker Eric S. Raymond writes in his Jargon File that EBCDIC was almost universally loathed by early hackers and programmers because of its multitude of different versions, none of which resembled the other versions, and that IBM produced it in direct competition with the already-established ASCII.

The Jargon File 4.4.7 gives the following definition:

Another popular complaint is that the EBCDIC alphabetic characters follow an archaic punched card encoding rather than a linear ordering like ASCII. One consequence of this is that incrementing the character code for "I" does not produce the code for "J", and likewise there is a gap between the codes for "R" and "S". Thus programming a simple control loop to cycle through only the alphabetic characters is problematic.

These incompatibilities were also the source of many jokes. One such joke went:

Professor: "So the American government went to IBM to come up with an encryption standard, and they came up with—"
Student: "EBCDIC!"

A reference to the EBCDIC character set is made in the classic Infocom adventure game Zork II. In the "Machine Room", there is a collection of ancient computers and other machines of uncertain purpose. The following is the description of the room, with EBCDIC used to imply an incomprehensible language:

See also[link]

• EBCDIC-codepages with Latin-1-charset
• codepage 037 (English, Portuguese)
• codepage 285 (Ireland, United Kingdom)
• UTF-EBCDIC

References[link]

External links[link]

• Character Data Representation Architecture (CDRA) from IBM Contains IBM's official information on codepages and charsets.
  • Codepage 37
  • Codepage 1047
• F.0 Appendix F. Code Pages from AS/400 International Application Development V4R2
• ICU Converter Explorer Contains more information about EBCDIC derived from IBM's CDRA, including DBCS EBCDIC (Double Byte Character Set EBCDIC)
• ICU Charset Mapping Tables Contains computer readable Unicode mapping tables for EBCDIC and many other character sets
• ASCII/EBCDIC Conversion Table for HP 3000 MPE/iX Computer Systems
• EBCDIC character list, including decimal and hex values, symbolic name, and character/function
• iconv.com Online tool to convert from ASCII to/from EBCDIC
• EBCDIC-codepages with Latin-1-charset (JavaScript)

v t e Character encodings Character sets Early telecommunications ASCII ISO/IEC 646 ISO/IEC 6937 T.61 sixbit code pages Baudot code Morse code Chinese telegraph code ISO/IEC 8859 -1 -2 -3 -4 -5 -6 -7 -8 -9 -10 -11 -12 -13 -14 -15 -16 Bibliographic use ANSEL ISO 5426 / 5426-2 / 5427 / 5428 / 6438 / 6861 / 6862 / 10585 / 10586 / 10754 / 11822 MARC-8 National standards ArmSCII CNS 11643 GOST 10859 GB 2312 HKSCS ISCII JIS X 0201 JIS X 0208 JIS X 0212 JIS X 0213 KPS 9566 KS X 1001 PASCII TIS-620 TSCII VISCII YUSCII EUC CN JP KR TW ISO/IEC 2022 CN JP KR CCCII MacOS codepages ("scripts") Arabic CentralEurRoman ChineseSimp / EUC-CN ChineseTrad / Big5 Croatian Cyrillic Devanagari Dingbats Farsi Greek Gujarati Gurmukhi Hebrew Icelandic Japanese / ShiftJIS Korean / EUC-KR Roman Romanian Symbol Thai / TIS-620 Turkish Ukrainian DOS codepages 437 720 737 775 850 852 855 857 858 860 861 862 863 864 865 866 869 Kamenický Mazovia MIK Iran System Windows codepages 874 / TIS-620 932 / Shift JIS 936 / GBK 949 / EUC-KR 950 / Big5 1250 1251 1252 1253 1254 1255 1256 1257 1258 1361 54936 / GB18030 EBCDIC codepages 37/1140 273/1141 277/1142 278/1143 280/1144 284/1145 285/1146 297/1147 420/16804 424/12712 500/1148 838/1160 871/1149 875/9067 930/1390 933/1364 937/1371 935/1388 939/1399 1025/1154 1026/1155 1047/924 1112/1156 1122/1157 1123/1158 1130/1164 JEF KEIS Platform specific ATASCII CDC display code DEC-MCS DEC Radix-50 Fieldata GSM 03.38 HP roman8 PETSCII TI calculator character sets WISCII ZX Spectrum character set Unicode / ISO/IEC 10646 UTF-8 UTF-16/UCS-2 UTF-32/UCS-4 UTF-7 UTF-1 UTF-EBCDIC GB 18030 SCSU BOCU-1 Miscellaneous codepages APL Cork HZ IBM code page 1133 KOI8 TRON Related topics control character (C0 C1) CCSID Character encodings in HTML charset detection Han unification ISO 6429/IEC 6429/ANSI X3.64 mojibake